Medical is closer: While there are dedicated certifications for medical, they are relatively close to the IEC 61508 industrial standards and so IEC certifications are often used as a stand-in for the equivalent medical certification.
http://ada-auth.org/standards/22rm/html/RM-B.html
AdaCore has a Rust toolchain:
https://www.adacore.com/gnatpro-rust
Edit: not so worried about the extensions, more worried they will keep re-releasing 1.68 forever with features added only as people clamor for them. And security fixes wedged into old code. That is in effect forking the language.
In any case, the compiler wouldn't be certified if they didn't vet the new features. These companies can't control what gets added to the language, and it might take longer than a year to vet future changes.
Their statement is an upfront, no-bull fyi about how reality works. I highly doubt it's a statement of intent to stagnate. It would kind of defeat the purpose of switching away from a stagnated language and ecosystem.
1. Stay on the last certified version until everything is certified.
2. Incorporate the parts that can be certified.
They're promising yearly updates. I'm asking what happens when a new upstream feature has already gone uncertified for one full year. Either they blow past the deadline and release nothing for over a year, or they ship what's currently available.
There's no third option. Ferrous doesn't have a time machine, and AdaCore is just explicitly saying that they'll give you what they have at least once a year.
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.
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.
https://news.ycombinator.com/threads?id=thesuperbigfrog&next...
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.
Correct, AdaCore / GNAT has extensions that are not part of the Ada standard:
https://docs.adacore.com/gnat_rm-docs/html/gnat_rm/gnat_rm/g...
I don't have a close relationship with AdaCore and do not know what they are planning for their Rust toolchain.
That said, I would be surprised if they do not add features to ensure Rust plays nicely with their other products and give their Rust toolchain competitive advantages in the safety critical space. I do not see any documentation or details on their website yet, but it also looks like their Rust toolchain is not released yet.