-
Notifications
You must be signed in to change notification settings - Fork 275
fix nullability of AssemblyEnumerator.GetTypes #5401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
SimonCropp
wants to merge
7
commits into
microsoft:main
Choose a base branch
from
SimonCropp:fix-nullability-of-AssemblyEnumerator.GetTypes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
91dcbf5
fix nullability of AssemblyEnumerator.GetTypes
SimonCropp 04148da
Merge branch 'main' into fix-nullability-of-AssemblyEnumerator.GetTypes
SimonCropp e9a7a08
Merge branch 'main' into fix-nullability-of-AssemblyEnumerator.GetTypes
SimonCropp b34eb51
Merge branch 'main' into fix-nullability-of-AssemblyEnumerator.GetTypes
SimonCropp 2ebfc48
Update TypeCache.cs
SimonCropp b6e3637
Update AssemblyEnumerator.cs
SimonCropp f6d41e3
Merge branch 'main' into fix-nullability-of-AssemblyEnumerator.GetTypes
SimonCropp File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a change in behavior.
Previously if
type
was null, we will go through thetry
, which will fail, then we get into thecatch
that will fail due tot.FullName
(it will throw NullReferenceException).The original intent is to probably ignore types that failed to load, but that as well wasn't a good design decision.
I think it's best in v4 if we just not catch any
ReflectionTypeLoadException
and let everything fail.