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

Turn off unused opens diagnostic analyzer in dev15.6 #4494

Closed
wants to merge 1 commit into from

Conversation

dsyme
Copy link
Contributor

@dsyme dsyme commented Mar 12, 2018

This is a proposed patch to dev15.6. See #4488

This diagnostic analyzer can be re-enabled once
(a) the analyzers run in priority order, see #4341
(b) the underlying code for unused opens is made performant, see #4488 and fsharp/fsharp-compiler-docs#830
(c) the underlying code for unused opens is made cancellable

@cartermp
Copy link
Contributor

The problem is that this will have to meet a servicing bar, i.e. demonstrably break customers in some way that they weren't before, or severely degrade their experience from the previous release such that this new one is unworkable. Given that there is already a workaround to turn it off, I suspect this does not meet that bar.

@dsyme dsyme changed the title Turn of unused opens diagnostic analyzer in dev15.6 Turn off unused opens diagnostic analyzer in dev15.6 Mar 12, 2018
@dsyme
Copy link
Contributor Author

dsyme commented Mar 12, 2018

@dotnet-bot test Ubuntu14.04 Release_fcs Build please

1 similar comment
@dsyme
Copy link
Contributor Author

dsyme commented Mar 12, 2018

@dotnet-bot test Ubuntu14.04 Release_fcs Build please

@dsyme
Copy link
Contributor Author

dsyme commented Mar 12, 2018

@cartermp Re servicing bar - I'll leave you to decide. It's the first thing I noticed when using 15.6 "as a customer". I suspect it wasn't in 15.3/15.4, but I don't have proof of that.

@dsyme dsyme closed this Mar 14, 2018
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.

2 participants