Fine-grained distinction of source-breaking vs. binary-breaking changes#133
Merged
Fine-grained distinction of source-breaking vs. binary-breaking changes#133
Conversation
…ble scoped type parameter resolution
…PE_CHANGED_INCOMPATIBLE with proper assignability logic
…-breaking METHOD_NOW_STATIC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This makes Roseau more accurate by separating source-breaking from binary-breaking changes where the previous BCs were too coarse.
FIELD_TYPE_ERASURE_CHANGEDfor binary incompatibilityFIELD_TYPE_CHANGED_INCOMPATIBLEfor source incompatibilityMETHOD_RETURN_TYPE_ERASURE_CHANGEDfor binary incompatibilityMETHOD_RETURN_TYPE_CHANGED_INCOMPATIBLEfor source incompatibilityMETHOD_NOW_STATICinto:METHOD_NOW_STATICfor binary incompatibilityMETHOD_OVERRIDABLE_NOW_STATICfor source incompatibility