C#: Fix assembly attribute extraction in standalone mode#14792
Merged
Conversation
3db94e5 to
7a001f4
Compare
michaelnebel
approved these changes
Nov 15, 2023
Contributor
michaelnebel
left a comment
There was a problem hiding this comment.
LGTM 👍
It will be interesting to see, if this yields crashes as well
The enumeration logic seems quite complicated (I just peeked the decompiled code). Does it make sense to run DCA to see if this has any semantical change that the tests didn't catch?
Contributor
Author
|
DCA doesn't show any change. |
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
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 PR tries to fix assembly attribute extraction in standalone mode. I can't reliably repro the issue, but occasionally we're seeing the below exception:
I don't know if this fix is really fixing the problem, but it avoids using
Microsoft.CodeAnalysis.SeparatedSyntaxList1.Enumerator.get_Current()`, which might be causing the issue.