6 ms·
Thank you. I wonder how long this will hold though? I would not like to see it get to a point where the language is fine but people aren't really sure what else
by greatgirl 6y ago
Thank you. I wonder how long this will hold though? I would not like to see it get to a point where the language is fine but people aren't really sure what else to do and just make changes for the hell of it.
In other words I think there needs to be a long term standardisation plan to keep the language stable, but for now this is a good step.
- steveklabnik 6y ago> I would not like to see it get to a point where the language is fine but people aren't really sure what else to do and just make changes for the hell of it. We never make changes for the hell of it. But also, all changes are purely additive at this point. The language is stable. It has been for years.
- greatgirl 6y agoIn that case I think keeping up very small additive changes is good, thanks for clearing up
- estebank 6y agoTo expand on Steve's point, code written in 1.0 style should continue to work indefinitely, modulo soundness fixes, lints and plain old bugs. You should only need to update at your own pace or because your dependencies force you to, and they shouldn't do so often if they care about supporting as many users as possible. Big changes, like async/await sugar or impl Trait or the ? operator are uncommon and they either make your code that much nicer to read or allow new constructs that were previously impossible.