- 01 7月, 2020 2 次提交
-
-
由 Tomáš Matoušek 提交于
-
由 Tomáš Matoušek 提交于
* Revert "Revert "Remove Razor IVTs (#43235)"" This reverts commit 0dc4f3da. * Remove Microsoft.VisualStudio.LanguageServices.Razor.RemoteClient.csproj * Fix package
-
- 27 6月, 2020 2 次提交
-
-
由 Sam Harwell 提交于
-
由 Tomáš Matoušek 提交于
-
- 26 6月, 2020 7 次提交
-
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
Fixes #45452
-
由 Gen Lu 提交于
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
- 24 6月, 2020 2 次提交
- 23 6月, 2020 6 次提交
-
-
由 Jason Malinowski 提交于
A workspace can customize which changes are allowed to be applied through TryApplyChanges. There's a CanApplyChanges that generally is called with each type of change which you can opt in for. There is also a specific overloads for filtering specific changes to CompilationOptions or ParseOptions, since a host may support changing some of those but not all of them. This documents our existing behavior and adds tests to confirm the behavior. There were some Debug.Asserts() that are incorrect and are now fixed.
-
由 Gen Lu 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Gen Lu 提交于
-
由 Gen Lu 提交于
-
- 20 6月, 2020 1 次提交
-
-
由 Manish Vasani 提交于
First step towards #44408 1. Refactor IDE open file analysis so that we have a single place where we execute the analyzers for document analysis. I have preserved the existing IDE layer diagnostic caching in this PR, but it should hopefully go away in future when we move the diagnostic computation to OOP. 2. Perf improvement: Currently, we execute open file analyzers one at a time by making separate calls into CompilationWithAnalyzers. This identified overhead where we are recomputing lot of stuff with each call and missing semantic model/bound node cache hits. This PR simplifies the approach by invoking a single syntax/semantic call into CompilationWithAnalyzers with all relevant analyzers. This required adding a new public API to CompilationWithAnalyzers to return syntax/semantic diagnostics for a tree/model grouped by analyzers, which has been split into a separate commit. 3. Remove code for code fix support for CompilationEndAction diagnostics - these actions are not executed in the IDE live analysis, so the code was not executing. Additionally, we have identified that we never want to run these actions in IDE live analysis due to associated perf concerns. Future steps: 1. Move open file diagnostic analyzer execution to OOP 2. Remove IDE layer diagnostic caching, and rely on caching at OOP side 3. Investigate moving even compiler diagnostic computation to OOP - need to ensure responsiveness of refreshing compiler diagnostics on typing is not affected
-
- 19 6月, 2020 1 次提交
-
-
由 Gen Lu 提交于
-
- 18 6月, 2020 3 次提交
-
-
由 Gen Lu 提交于
-
由 Gen Lu 提交于
Since they are already from the same compilation that triggered completion.
-
由 Cyrus Najmabadi 提交于
-
- 17 6月, 2020 5 次提交
-
-
由 Gen Lu 提交于
-
由 Gen Lu 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Fredric Silberberg 提交于
-
由 Cyrus Najmabadi 提交于
-
- 16 6月, 2020 1 次提交
-
-
由 Gen Lu 提交于
All array types for one elemnt type is consider same in our index. e.g. int[], int[][] and int[,] are just represent as int[]
-
- 15 6月, 2020 1 次提交
-
-
由 Joey Robichaud 提交于
-
- 13 6月, 2020 2 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 12 6月, 2020 3 次提交
-
-
由 Joey Robichaud 提交于
-
由 Joey Robichaud 提交于
-
由 Cyrus Najmabadi 提交于
-
- 11 6月, 2020 4 次提交
-
-
由 CyrusNajmabadi 提交于
Update src/Workspaces/Core/Portable/FindSymbols/FindReferences/FindReferencesSearchEngine_ProjectProcessing.cs
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-