Skip to content
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

Create DiagnosticInfo as an incremental Diagnostic replacement type. #86908

Merged
merged 7 commits into from
Jun 2, 2023

Conversation

jtschuster
Copy link
Member

Creates DiagnosticInfo record to replace Diagnostic in the incremental pipeline to work around dotnet/roslyn#68291

@ghost
Copy link

ghost commented May 30, 2023

Tagging subscribers to this area: @dotnet/interop-contrib
See info in area-owners.md if you want to be subscribed.

Issue Details

Creates DiagnosticInfo record to replace Diagnostic in the incremental pipeline to work around dotnet/roslyn#68291

Author: jtschuster
Assignees: jtschuster
Labels:

area-System.Runtime.InteropServices

Milestone: -

Copy link
Member

@pavelsavara pavelsavara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Do I understand correctly that instances of the DiagnosticInfo are created only if there is something wrong with the compiled code, so probably rarely ?

@jtschuster
Copy link
Member Author

Do I understand correctly that instances of the DiagnosticInfo are created only if there is something wrong with the compiled code, so probably rarely ?

Yes, the DiagnosticInfo instances are made by the generators when it runs into an issue with the user's code, which shouldn't be often.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants