Skip to content

Warning or error is raised when consuming IL Event with an Obsolete attribute#14006

Merged
vzarytovskii merged 5 commits into
dotnet:mainfrom
edgarfgp:no-error-or-warning-is-raised-when-consuming-il-eevents
Oct 4, 2022
Merged

Warning or error is raised when consuming IL Event with an Obsolete attribute#14006
vzarytovskii merged 5 commits into
dotnet:mainfrom
edgarfgp:no-error-or-warning-is-raised-when-consuming-il-eevents

Conversation

@edgarfgp

@edgarfgp edgarfgp commented Oct 1, 2022

Copy link
Copy Markdown
Contributor

This PR fixes a BUG mentioned on #13511 (comment)

@edgarfgp edgarfgp marked this pull request as ready for review October 1, 2022 10:37
@edgarfgp edgarfgp changed the title No warning or error is raised when consuming IL Event with an Obsolete attribute Warning or error is raised when consuming IL Event with an Obsolete attribute Oct 2, 2022
Comment thread src/Compiler/Checking/CheckExpressions.fs Outdated

@vzarytovskii vzarytovskii left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Just small comment on matching.
As a rule of thumb, we probably shouldn't ever match on any DUs from infos.

@T-Gro

T-Gro commented Oct 4, 2022

Copy link
Copy Markdown
Member

Just small comment on matching. As a rule of thumb, we probably shouldn't ever match on any DUs from infos.

I am planning more encapsulation around infos, Don lure me into this and I think it makes sense.
Reducing the amount of matching on Type/Method-Info, as well as amount of publicly exposed props from it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants