-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Remove incorrect flag setting #88878
Conversation
/azp run runtime-coreclr crossgen2 |
No pipelines are associated with this pull request. |
/azp run runtime-coreclr crossgen2 |
No pipelines are associated with this pull request. |
/azp run runtime-coreclr crossgen2 |
No commit pushedDate could be found for PR 88878 in repo dotnet/runtime |
/azp run runtime-coreclr crossgen2 |
No pipelines are associated with this pull request. |
/azp run runtime-coreclr crossgen2 |
No pipelines are associated with this pull request. |
/azp run runtime-coreclr crossgen2 |
No commit pushedDate could be found for PR 88878 in repo dotnet/runtime |
9009978
to
47d69ae
Compare
/azp run runtime-coreclr crossgen2 |
No pipelines are associated with this pull request. |
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.
Looks good.
This was added in #85743 (comment). Setting this flag is not the right thing to do. It sweeps issues under the carpet. Also, we're only doing it for signature type variables, not method variable. And since no tests seem to be failing, it might not even be necessary.