4 ms·

The direct competition between Ferrocene and AdaCore should take care of that. In any case, the compiler wouldn't be certified if they didn't vet the new featu

The direct competition between Ferrocene and AdaCore should take care of that. 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.

galangalalgol 3y ago
I can imagine no use case where ripping out features from upstream reduces risk vs adding it. I agree it makes no sense to stagnate, but I am familiar with the certified compiler space, and what I have described is exactly what I have witnessed. Compilers that are based on ancient versions of open source compilers, and have code incorporated from various point releases since then to minimize the amount of recertification necessary.
- sheepshear 3y ago
  What happens when a new feature holds up the certification process for some reason? There are only two possible options, and they both suck: 1. Stay on the last certified version until everything is certified. 2. Incorporate the parts that can be certified.
  - galangalalgol 3y ago
    The ferrous option appears to be 3. upstream changes that make certification of the new feature easier and then proceed.
    - sheepshear 3y ago
      If that's still an option, then they haven't reached the point yet where they have to choose. 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.

galangalalgol 3y ago

I can imagine no use case where ripping out features from upstream reduces risk vs adding it. I agree it makes no sense to stagnate, but I am familiar with the certified compiler space, and what I have described is exactly what I have witnessed. Compilers that are based on ancient versions of open source compilers, and have code incorporated from various point releases since then to minimize the amount of recertification necessary.

sheepshear 3y ago
What happens when a new feature holds up the certification process for some reason? There are only two possible options, and they both suck: 1. Stay on the last certified version until everything is certified. 2. Incorporate the parts that can be certified.
- galangalalgol 3y ago
  The ferrous option appears to be 3. upstream changes that make certification of the new feature easier and then proceed.
  - sheepshear 3y ago
    If that's still an option, then they haven't reached the point yet where they have to choose. 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.