Filesystem-oriented flags: sad, messy and not going away
Filesystem-oriented flags: sad, messy and not going away
Posted Mar 17, 2020 7:02 UTC (Tue) by areilly (subscriber, #87829)In reply to: Filesystem-oriented flags: sad, messy and not going away by areilly
Parent article: Filesystem-oriented flags: sad, messy and not going away
I know that rust is versioning its releases too, but I don't know whether that actually allows for the linking and use of code written against different language versions, the way racket does. Racket code can import and use r5rs or r6rs or experimental-dialect code, which is cool. I suppose that C++ can do similarly for separately compiled object files, but it can't include old headers into new code, and python3 can't import python2 modules, which IMO is a terrible shame.
Posted Mar 17, 2020 15:15 UTC (Tue)
by farnz (subscriber, #17727)
[Link]
The equivalent in Rust is Editions; you can freely link code between different editions (currently only 2015 and 2018), but the compiler will translate each translation unit (crate in Rust) according to the edition you have specified for that crate.
Nothing, however, stops a Rust 2015 crate using a Rust 2018 crate as a dependency, or vice-versa, and you can freely share data types between the two editions. The only problem is that you might have to use r#identifier syntax if one crate uses a reserved word as an identifier.
Filesystem-oriented flags: sad, messy and not going away