-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rust-standard/ #11
Comments
Thanks for the article, 99% of the people who say "there's no standard for Rust!" have no reasons to worry about this as by the time they're good enough at programming Rust to write some safety-critical software a standard will have been finished (Ferrocene is opting for 2023). |
Never income for standardization organizations. It would be his death .... |
It's a lot of text but finally I derive that Rust is standardized, just not by an international standardization organization. A more formal language specification (in natural language just like in other languages) corresponds just to a higher maturity level of standardization. Ideally a language just by specified by a machine-checkable formal language so that source and binary code can be formally verified more easily. |
Thank you for the explanation. |
Do we need a "Rust Standard"? - Mara's Blog
Languages like C and C++ are standardized. They are fully specified in an internationally recognized standards document. Languages like Python, Swift and Rust do not have such a standards document.
Should Rust be standardized? Why, or why not? In this blog post, I try to explain why I do think we need an accurate specification, why I do not think we need “standardization” (depending on your definition), and give an overview of the current state of Rust’s stability and specification efforts.
https://blog.m-ou.se/rust-standard/
The text was updated successfully, but these errors were encountered: