Unsafe evolution: warn for using the attribute under legacy rules and some cleanup#82456
Open
jjonescz wants to merge 12 commits intodotnet:features/UnsafeEvolutionfrom
Open
Unsafe evolution: warn for using the attribute under legacy rules and some cleanup#82456jjonescz wants to merge 12 commits intodotnet:features/UnsafeEvolutionfrom
jjonescz wants to merge 12 commits intodotnet:features/UnsafeEvolutionfrom
Conversation
It still makes sense to have unsafe blocks around all pointers, hence we don't hint to enable the updated memory safety rules in the legacy errors.
It's not relevant since we use an attribute now.
jjonescz
changed the title
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.
Test plan: #81207
Related speclet update: dotnet/csharplang#9999
Commits should be mostly self-contained.