- 09 9月, 2015 5 次提交
-
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Jason Malinowski 提交于
project.json Fixes
-
- 07 9月, 2015 1 次提交
-
-
由 Andy Gocke 提交于
Update the project.lock.json for FakeSign and upload a new nuget zip
-
- 05 9月, 2015 25 次提交
-
-
由 Kevin Halverson 提交于
#load directives...
-
由 Kevin Halverson 提交于
It isn't needed, as the Workspace will notice changes in the Compilation due to #loads.
-
由 Kevin Halverson 提交于
-
由 Kevin Halverson 提交于
-
由 Kevin Halverson 提交于
-
由 Kevin Halverson 提交于
Tidy up nuget artifacts for ResultProviders...
-
由 VSadov 提交于
Fixes a subtle bug in branch optimizer.
-
由 VSadov 提交于
Making stack scheduling optimizations more robust and fixing #4828
-
由 Manish Vasani 提交于
Performance improvements for the v2 analyzer driver
-
由 Jonathon Marolf 提交于
Using correct case in-sensitive comparer Fixes #4782
-
由 Kevin Halverson 提交于
-
由 Andrew Casey 提交于
Address PR feedback
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 Andy Gocke 提交于
-
由 Jonathon Marolf 提交于
-
由 Jonathon Marolf 提交于
Remove check for 'IgnoreCase In CSharpAddImportCodeFixProvider we explicitly override IgnoreCase to be false. Therefore, we will never use a case in-sesitive comparer.
-
由 CyrusNajmabadi 提交于
Prioritize uncommenting single line comments over multi-line comments. Fixes: #548
-
由 Manish Vasani 提交于
1) Reduce number allocations in the analyzer driver that show up perf traces for Picasso. 2) Currently we maintain a cache of CompilationWithAnalyzers for projects being actively analyzed. This is causing the VM to rise and also forcing GC to kick in at different phases causing regressions at various scenarios. The fix is to just create a new CompilationCompilationWithAnalyzers instance for each document/project analysis request.
-
由 AlekseyTs 提交于
Add support for multi-dimensional arrays of rank 1 to C# compiler.
-
由 AlekseyTs 提交于
Fixes #4924.
-
由 CyrusNajmabadi 提交于
Start outlining span after all the whitespace on the target token.
-
由 Brett Forsgren 提交于
list exceptions from the doc comments when showing quick info
-
由 vsadov 提交于
-
由 vsadov 提交于
"branch over branch" optimization eliminates chains of trivial basic blocks from the graph, which is correct as long as trivial blocks are not reachable individually from outside via branches. The "same as next" optimization can make a block trivial and if it was targeted by a branch, break the assumption, leading to a rare situation of some branches having stale offsets. The fix makes sure if a block becomes trivial, its labels are moved to the next nontrivial block. Fixes #4838 Fixes #4839
-
- 04 9月, 2015 9 次提交
-
-
由 Dustin Campbell 提交于
Fix Visual Basic Workflow v1 projects when events are hooked up
-
由 Dustin Campbell 提交于
-
由 Charles Stoner 提交于
Update comment from b60a2b93
-
由 Jonathon Marolf 提交于
Fix inserting using inside namespace Fixes #3080
-
由 Charles Stoner 提交于
-
由 Jonathon Marolf 提交于
speculative semantic model determine if we should use the fully qualified name or not. What this approach failed to account for was if the name was going to be simplified further due to the containing namespace. To Fix this we run the simplifier over our document and check if there are any changes made to the namespace. If this is the case, then we re-sort the usings according to the simplified name.
-
由 Jonathon Marolf 提交于
Generate inaccessible getters and setters Fixes #2407
-
由 Cyrus Najmabadi 提交于
-
由 Andy Gocke 提交于
NuGet restore output is blowing up our log files, so this should output only errors.
-