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

Remove Pure attribute from System.Collections.Immutable #35118

Merged
merged 2 commits into from
Apr 27, 2020

Conversation

ericstj
Copy link
Member

@ericstj ericstj commented Apr 17, 2020

No description provided.

@ghost
Copy link

ghost commented Apr 17, 2020

Tagging subscribers to this area: @eiriktsarpalis
Notify danmosemsft if you want to be subscribed.

@ericstj
Copy link
Member Author

ericstj commented Apr 17, 2020

Fixes #28488

@ericstj ericstj added the breaking-change Issue or PR that represents a breaking API or functional change over a prerelease. label Apr 17, 2020
@ericstj
Copy link
Member Author

ericstj commented Apr 17, 2020

Tagged as breaking since the issue mentions that the purpose of this is to raise CA1806 warnings.

@ericstj ericstj changed the title Preserve Pure attribute in System.Collections.Immutable Remove Pure attribute from System.Collections.Immutable Apr 20, 2020
@ericstj
Copy link
Member Author

ericstj commented Apr 20, 2020

So I changed the title of this PR to remove the usage of Pure. @AArnott / @stephentoub what do you think is the right way to track the scenario here?

@stephentoub stephentoub removed the breaking-change Issue or PR that represents a breaking API or functional change over a prerelease. label Apr 20, 2020
@stephentoub
Copy link
Member

stephentoub commented Apr 20, 2020

what do you think is the right way to track the scenario here?

First decide what the scenario is 😄 If it's "warn when methods whose results shouldn't be ignored are ignored", we should have an issue tracking/designing it (I think @terrajobst already opened one somewhere for that). If the scenario is something else, well, same answer :)

@ericstj
Copy link
Member Author

ericstj commented Apr 20, 2020

First decide what the scenario is 😄 If it's "warn when methods whose results shouldn't be ignored are ignored", we should have an issue tracking/designing it (I think @terrajobst already opened one somewhere for that). If the scenario is something else, well, same answer :)

Well I was expecting @AArnott to help fill that in once we have some direction about where to do so. I imagine the one you described is close enough to what I'm imagining @AArnott is looking for. @terrajobst can you link us up with that issue?

@terrajobst
Copy link
Member

I imagine the one you described is close enough to what I'm imagining @AArnott is looking for. @terrajobst can you link us up with that issue?

That would be #34098. Based on the experience of @stephentoub & @jaredpar in Midori I'd say the direction of having an attribute like [DoNotIgnoreReturnValue] seems like the right direction.

@stephentoub stephentoub merged commit 90cb824 into dotnet:master Apr 27, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 9, 2020
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.

6 participants