Skip to content

"Microsoft.FSharp" namespace considered unused if "Microsoft" is removed #3095

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

Closed
asik opened this issue May 20, 2017 · 3 comments
Closed

"Microsoft.FSharp" namespace considered unused if "Microsoft" is removed #3095

asik opened this issue May 20, 2017 · 3 comments
Labels
Area-LangService-API Bug Impact-Medium (Internal MS Team use only) Describes an issue with moderate impact on existing code.
Milestone

Comments

@asik
Copy link
Contributor

asik commented May 20, 2017

Writing "Microsoft" is optional in namespaces beginning with "Microsoft.FSharp". However, this seems to confuse the unused namespace finder:

image

In this case, the namespace should not be flagged as unused, as removing it will cause the code not to compile.

Visual FSharp Tools 15.4.1.17051001.

@vasily-kirichenko
Copy link
Contributor

I believe I fixed this already :(

@cartermp cartermp added this to the VS 2017 Updates milestone May 21, 2017
@cartermp cartermp added the Bug label May 21, 2017
@dsyme dsyme added the Impact-Medium (Internal MS Team use only) Describes an issue with moderate impact on existing code. label Jun 20, 2017
@BentTranberg
Copy link

BentTranberg commented Jul 23, 2017

Is this an effect of bug #3347 / #3306 ? I think so.

@cartermp
Copy link
Contributor

I believe this has been fixed - I cannot reproduce it anymore in 15.6 Preview 5:

works

@cartermp cartermp modified the milestones: VS 2017 Updates, 15.6 Jun 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-LangService-API Bug Impact-Medium (Internal MS Team use only) Describes an issue with moderate impact on existing code.
Projects
None yet
Development

No branches or pull requests

5 participants