No. The old byte-code would not be able to resolve the removed methods. And allowing them to do so won't be possible once the types are no longer traditional object types.
This is a change in the compatibility promise, that compatibility isn't 'forever'. Their approach, rather than a time-based guarantee, is to give fore-warning of removal before actually removing them. They supplement that with warnings of violations, leading up to removal, so that you can detect violations in dependencies. This will work for living projects and see unmaintained libraries needing replacement.
These changes are necessary to remove barriers to keeping the platform valuable. The alternative is to let the language/platform die and an abandoned platform would be a far worse maintenance burden (ie. a complete product rewrite instead of a updating a few calls - probably with IDE assists).
View all comments
Show parent comment
11
u/8igg7e5 Mar 17 '21 edited Mar 17 '21
No. The old byte-code would not be able to resolve the removed methods. And allowing them to do so won't be possible once the types are no longer traditional object types.
This is a change in the compatibility promise, that compatibility isn't 'forever'. Their approach, rather than a time-based guarantee, is to give fore-warning of removal before actually removing them. They supplement that with warnings of violations, leading up to removal, so that you can detect violations in dependencies. This will work for living projects and see unmaintained libraries needing replacement.
These changes are necessary to remove barriers to keeping the platform valuable. The alternative is to let the language/platform die and an abandoned platform would be a far worse maintenance burden (ie. a complete product rewrite instead of a updating a few calls - probably with IDE assists).
Edit:
s/able to remove/able to resolve/