Add analyzer info for detecting IntPtr/UintPtr behavioral changes #64485
Conversation
This file contains 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
333fred
reviewed
Oct 4, 2022
Co-authored-by: Fred Silberberg <fred@silberberg.xyz>
333fred
approved these changes
Oct 4, 2022
ghost
added this to the 
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to Prevent behavioral change in built-in operators for IntPtr and UIntPtr analyzer
Initially we wanted to warn for potential behavioral changes detected, but after testing the analyzer with runtime and few other repos we decided to degrade the analysis level to info as there were very few cases that could cause a real behavioral change.
As now users will not be warned if their code had a potential behavioral changes we want to inform them that there is an analyzer that they could use for detecting such breaking behavioral changes in this doc (I did not found any other breaking change doc except this one)
CC @jeffhandley @tannergooding