When safety reasons call for a change to API in the safety environment, the change is typically rejected if it does not maintain backward compatibility. A compatibility-breaking change to API should be rejected only if safety analysis shows that maintaining compatibility is actually safer.
For reference, general issue "Design goals" is defined as issue #26.
When safety reasons call for a change to API in the safety environment, the change is typically rejected if it does not maintain backward compatibility. A compatibility-breaking change to API should be rejected only if safety analysis shows that maintaining compatibility is actually safer.
For reference, general issue "Design goals" is defined as issue #26.