- 21 5月, 2015 2 次提交
-
-
由 Jared Parsons 提交于
Use correct count in ReplaceSeparator
-
由 Jared Parsons 提交于
The bounds checking code for the existing separator has no need to do an upper bound check on `index`. The IndexOf method will return -1 or a valid index into nodesWithSeps. Hence the comparison with `this.Count` here was both unnecessary and incorrect (should have been `nodesWithSeps.Count`). closes #2630
-
- 20 5月, 2015 21 次提交
-
-
由 Tomáš Matoušek 提交于
Update PublicAPI.txt to reflect recent changes to Scripting APIs.
-
由 Tomas Matousek 提交于
-
由 Heejae Chang 提交于
added build only filter support to error list
-
由 Andrew Casey 提交于
Refine hoisted local scopes in async methods
-
由 Tomáš Matoušek 提交于
Make APIs related to scripting and interactive internal for RTM
-
由 Heejae Chang 提交于
Improve undo stack titles for suggestions applied via light bulb
-
-
由 Tom Meschter 提交于
Use assembly name for analyzer ID Use the actual assembly name for `AnalyzerFileReference.Id`, instead of a lowercase version of the file name. There are places we are currently using `AnalyzerReference.Id` when what we may want is `AnalyzerReference.DisplayName`. Notably, in the rule set editor. This means that after my recent change to simply return the lowercase version of the analyzer assembly's file name, the rule set editor started showing "microsoft.codeanalysis.analyzers.dll" instead of "Microsoft.CodeAnalysis.Analyzers". The "right" solution would probably involve an API to map from an ID back to an `AnalyzerReference`, and then using the `DisplayName` in the rule set editor instead of the `Id`. At this stage in the release cycle, however, I'm going with a simpler solution: make `AnalyzerFileReference` return the same value for `Id` and `DisplayName`, and get that value by reading the assembly name from the file itself, like we used to. Fixes #2781 and #2782.
-
由 Charles Stoner 提交于
Fix typos
-
由 Charles Stoner 提交于
-
由 Tomáš Matoušek 提交于
Fix analyzer type load error reporting, API
-
由 Tomas Matousek 提交于
-
由 AlekseyTs 提交于
Visit InitialValue as rvalue in AbstractFlowPass(Of ).VisitFieldOrPropertyInitializer.
-
由 Tomas Matousek 提交于
-
由 Andrew Casey 提交于
Old: Scopes followed the bound tree, so the outermost scope was within the try-catch block synthesized in async MovedNext methods. New: If the entire try block would be a hoisted local scope, we remove the marker node (BoundStateMachineScope) and insert a new one around the entire method body. Upshot: hoisted locals are still in scope when stopped on method closing braces.
-
由 Kevin Halverson 提交于
Exception)...
-
由 Charles Stoner 提交于
Fix typos
-
由 Jared Parsons 提交于
Change pipe checksum to SHA256
-
由 Kevin Halverson 提交于
Implement Dynamic View expansion... (fixes #1743)
-
由 Kevin Halverson 提交于
-
由 Tom Meschter 提交于
Use the actual `AssemblyIdentity` for `AnalyzerFileReference.Id`, instead of a lowercase version of the file name. Also use `AssemblyIdentity.Name` as the `DisplayName`. If we can't read the file for whatever reason, fall back to strings generated from the file path. Fixes #2781 and #2782.
-
- 19 5月, 2015 17 次提交
-
-
由 Tom Meschter 提交于
Fix nulls in AnalyzerDependencyChecker. Currently we use a `Task.FromResult(null)` as a sentinel task before a real dependency check has been queued up. This works fine until we try to access the results of this task, and things blow up. Instead, we should create an AnalyzerDependecyResults.Empty singleton, and create a task from that. Also, this change catches all exceptions coming out of `AnalyzerDependencyChecker`, to avoid bringing down VS.
-
由 Tomáš Matoušek 提交于
Disable Deterministic PDB GUID generation for RTM
-
由 AlekseyTs 提交于
Fixes #2896.
-
由 Jonathon Marolf 提交于
Only return a fix if the assembly identity matches the diagnostic mes…
-
由 Jonathon Marolf 提交于
-
由 John Hamby 提交于
Don't leak Workspace objects from AnalyzerAndOptions
-
由 Charles Stoner 提交于
-
由 Charles Stoner 提交于
-
由 Charles Stoner 提交于
-
由 John Hamby 提交于
-
由 Jonathon Marolf 提交于
-
由 Balaji Krishnan 提交于
Add tests for #976. The actual fix for this was in the compiler #2540. Introduce local on interpolated string expressions should not generate a constant, but a variable.
-
由 Balaji Krishnan 提交于
Add tests for #976. The actual fix for this was in the compiler #2540. Introduce local on interpolated string expressions should not generate a constant, but a variable.
-
由 Matt Warren 提交于
Guard visitors against stack overflow exceptions
-
由 Tom Meschter 提交于
Currently we use a `Task.FromResult(null)` as a sentinel task before a real dependency check has been queued up. This works fine until we try to access the results of this task, and things blow up. Instead, we should create an AnalyzerDependecyResults.Empty singleton, and create a task from that. Also, this change catches all exceptions coming out of `AnalyzerDependencyChecker`, to avoid bringing down VS.
-
由 Heejae Chang 提交于
-
由 AlekseyTs 提交于
Handle BoundSequence as an assignment target in CodeGenerator.EmitAssignmentExpression.
-