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

VS 16.5 Tooling Performance #8255

Closed
5 tasks done
cartermp opened this issue Jan 17, 2020 · 1 comment
Closed
5 tasks done

VS 16.5 Tooling Performance #8255

cartermp opened this issue Jan 17, 2020 · 1 comment

Comments

@cartermp
Copy link
Contributor

cartermp commented Jan 17, 2020

This is an overarching issue that we're using to track F# tooling performance in VS up to VS 16.5. I expect these to positively impact other F# editors. Much of this work is actually in the compiler, as some things that are fine in a command-line scenario end up costing us dearly in a tooling scenario.

These are all filed based on data gathered from ETL traces with a solution loaded into Visual Studio, or are related to an issue where data was gathered in this way and determined to also be relevant. other issues labeled Tenet-Performance that are not listed here are not necessarily gathered in this way.

@cartermp
Copy link
Contributor Author

All other tracking issues: #6866

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

No branches or pull requests

1 participant