3 ms·
>> That is in effect forking the language. It feels like the effectiveness and success of Rust could make that happen. Different industries have different nee
by thesuperbigfrog 3y ago
>> That is in effect forking the language.
It feels like the effectiveness and success of Rust could make that happen.
Different industries have different needs and will want the language to meet their needs.
Rust needs more funding, labor, and organization to create an official language standard to prevent it from fragmenting.
- galangalalgol 3y agoFerrous created a language specification. https://github.com/ferrocene/specification https://github.com/ferrocene/specification They do say any differences between it and upstream behavior or documentation is a defect in the spec, not upstream. So it isn't authoritative. Unless we all decide it is.
- thesuperbigfrog 3y agoThey have explicitly stated that a Rust language specification is a non-goal for Ferrocene: https://news.ycombinator.com/threads?id=thesuperbigfrog&next=37769361# https://news.ycombinator.com/threads?id=thesuperbigfrog&next...
- Argorak 3y agoThere's an ongoing discussion about potential adoption into upstream, though. The thing here is: it would be harmful if we, Ferrous Systems, claimed or even be confused with a more general Rust spec. That's a) the privilege of the Rust project and b) problematic if consumers were to understand it that way.
- zozbot234 3y agoDoesn't Rust have a Reference manual already? A "spec" just wouldn't be very meaningful given the lack of independent implementations. But to the extent that the reference manual doesn't suffice for documenting the language, that's a defect which could and should be fixed.
- deleted 3y ago[deleted]
- sheepshear 3y agoThe manual isn't directly consumable by formal processes. The compiler design doesn't have to be influenced by a specification, but it does have to be described by one.