Adds an analyzer/fixer to inform the user when the compiler silently inserts a fallible explicit cast.#82039
Merged
CyrusNajmabadi merged 12 commits intodotnet:mainfrom Jan 17, 2026
Merged
Conversation
dibarbet
approved these changes
Jan 16, 2026
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
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.
based on discussion dotnet/csharplang#9917.
There are cases where only one explicit cast is written in source, but two may be inserted int eh final code. Both of these may fail for different reasons, and the user may be unaware of the inner cast and the impact it may have.
This analyzer let's you know when that is happening, and recommends moving to make both casts explicit in source so that the source is clear about what it is doing.