Add sealed type guidance to backwards compatibility guidelines#42
Open
jamiesanson wants to merge 1 commit into
Open
Add sealed type guidance to backwards compatibility guidelines#42jamiesanson wants to merge 1 commit into
jamiesanson wants to merge 1 commit into
Conversation
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.
I really like these backwards compatibility guidelines, and figured I'd contribute a few words around a principle we've been applying to library development - take care when using sealed types to avoid source incompatible changes.
I have noticed that these guidelines focus on binary compatibility for the most part, so feel free to take or leave this change!