[Info-vax] Rust as a HS language, was: Re: Quiet?

[Dan Cross]

In article <624b909b$0$703$14726298 at news.sunsite.dk>,
Arne Vajhøj  <arne at vajhoej.dk> wrote:
>On 4/4/2022 8:35 PM, Dan Cross wrote:
>> In article <t2fc4n$fml$3 at dont-email.me>,
>> Simon Clubley  <clubley at remove_me.eisner.decus.org-Earth.UFP> wrote:
>>> But other languages are also evolving over time, and they do it in
>>> a way that guarantees the next language variant is just another
>>> language mode in the existing compilers. That means I know I can still
>>> compile code written to that old language variant in the years to come.
>>>
>>> If the Rust language isn't going through a formal language standards
>>> process, how do I know that I can compile existing Rust code in
>>> 5/10/20 years time ?
>
>> As for the, "how can I be sure my code will compile..." question
>> have a look at Rust "editions", that are per-crate attributes.
>> They provide exactly the sort of guarantees you are looking for.
>
>This thing:
>
>https://doc.rust-lang.org/edition-guide/editions/index.html
>
>?
>
>It actually looks like Rust do prioritize compatibility.

Yup. That's it. They give pretty strict guarantees of
backwards compate for the stable parts of the language.
They saw the messes in Python on other languages, and
consciously sought to avoid them.

	- Dan C.