Uh oh!
There was an error while loading. Please reload this page.
add more tests for SRTP resolution - #8318
Merged
Merged
Conversation
dsyme
commented
Jan 22, 2020
ContributorAuthor
cartermp
approved these changes
Jan 22, 2020
nosami pushed a commit
to xamarin/visualfsharp
that referenced
this pull request
Feb 23, 2021
* add more tests * two new tests
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 adds four cases - one positive and three negative - related to SRTP constraint resolution
The aim is to pin down existing behaviour so we know if things change in the future, especially in subtle interactions with things like whether a type is sealed or not.