On Wed, Jan 10, 2024 at 3:52 PM <rsbecker@xxxxxxxxxxxxx> wrote: > > On Wednesday, January 10, 2024 5:26 PM, Taylor Blau wrote: > >On Wed, Jan 10, 2024 at 05:15:53PM -0500, rsbecker@xxxxxxxxxxxxx wrote: > >> Just a brief concern: Rust is not broadly portable. Adding another > >> dependency to git will remove many existing platforms from future releases. > >> Please consider this carefully before going down this path. > > > >I was hoping to hear from you as one of the few (only?) folks who participate on > >the list and represent HPE NonStop users. > > > >I'm curious which if any of the compiler frontends that I listed in my earlier email > >would work for you. > > Unfortunately, none of the compiler frontends listed previously can be built for NonStop. These appear to all require gcc either directly or transitively, which cannot be ported to NonStop. I do not expect this to change any time soon - and is outside of my control anyway. An attempt was made to port Rust but it did not succeed primarily because of that dependency. Similarly, Golang is also not portable to NonStop because of architecture assumptions made by the Go team that cannot be satisfied on NonStop at this time. If some of the memory/pointer issues are the primary concern, c11 might be something acceptable with smart pointers. C17 will eventually be deployable, but is not available on most currently supported OS versions on the platform. Would you be okay with the following alternative: requiring that all Rust code be optional for now? (In other words, allow you to build with USE_RUST=0, or something like that. And then we have both a Rust and a C implementation of anything that is required for backward compatibility, while any new Rust-only stuff would not be included in your build.)
