Originally posted by SpyroRyder
View Post
Announcement
Collapse
No announcement yet.
There Are Renewed Discussions About Having Rust Language Support Within GCC
Collapse
X
-
- Likes 2
-
Originally posted by Candy View PostIt will end the same death as gcj did. Rust is a language that no one uses.
I know John Paul has been working on bringing Rust to m68k. Maybe he'll achieve that quicker via this route.Last edited by Chewi; 29 December 2019, 12:13 PM.
- Likes 3
Comment
-
Originally posted by SpyroRyder View Post
spec and standard are different things though. It wouldnt take much for the Rust devs to say "this is the spec for Rust 2020, we shall also abide by it and all api/functional changes will now be a part of the 2021 branch" or something similar. They wont though cause the modern way of doing things is to have one dev team manage the full stack thus allowing everythong to respond to change quicker. Same reason you have to use Cargo and cant effectively build proper support into Meson and CMake
They already do though, see Rust 2015 & Rust 2018.
Comment
-
Originally posted by Candy View PostIt will end the same death as gcj did. Rust is a language that no one uses.
- Likes 1
Comment
-
Originally posted by Candy View PostIt will end the same death as gcj did.
Rust is a language that no one uses.
- Likes 3
Comment
-
Originally posted by Almindor View Post
Rust has stabilized Async/Await recently, not sure if you mean something else with "pinned down" here tho.
I'd say Rust is "there" now, I don't think there are many core language features missing apart maybe for const generics which once done will fix a LOT of inconsistencies and headaches and make the core nice and coherent.
Either way, I think it's up to the language developers/maintainers to say when they still have significant changes to make and when the whole thing is solid enough to become spec/standard worthy.
Comment
-
I think everyone would like some form of LTS release for the Rust ecosystem, but the language is still rapidly evolving and there isn't enough money to make this happen. The best idea I've heard of for creating a more stable target for Rust is versioning MIR. Then Rust developers can keep adding new features as long as they can be boiled off by the time the code is compiled down to MIR. This would minimize the investment needed for new compiler backends and high-assurance tooling.
But, again, some vendor would need to step-up and pay for that work.
Comment
Comment