Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upVS 2019 tooling performance #6096
Comments
cartermp
added
the
Tenet-Performance
label
Jan 14, 2019
cartermp
added this to the 16.0 milestone
Jan 14, 2019
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
#6076 is now completed. |
This comment has been minimized.
This comment has been minimized.
@cartermp Make it a task list! |
Feb 2, 2019
This was referenced
This comment has been minimized.
This comment has been minimized.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cartermp commentedJan 14, 2019
•
edited
This is an overarching issue that we're using to track F# tooling performance in VS. 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.