- 26 7月, 2019 1 次提交
-
-
由 Fredric Silberberg 提交于
Merge NullableAnnotation.NotApplicable and Disabled to None, and rename NullableFlowState.NotApplicable to None for consistency.
-
- 25 7月, 2019 1 次提交
-
-
由 Charles Stoner 提交于
Fixes #37310 Fixes #37279
-
- 24 7月, 2019 1 次提交
-
-
由 Chris Sienkiewicz 提交于
Fixes #35933
-
- 21 7月, 2019 2 次提交
-
-
由 Andy Gocke 提交于
-
由 Joey Robichaud 提交于
Also adds tests for various editorconfig inheritance/override scenarios
-
- 18 7月, 2019 2 次提交
-
-
由 Manish Vasani 提交于
Co-Authored-By: NSam Harwell <sam@tunnelvisionlabs.com>
-
由 Manish Vasani 提交于
IDE analyzer host invokes [CompilationWithAnalyzers.GetAnalyzerSemanticDiagnosticsAsync](http://source.roslyn.io/#q=CompilationWithAnalyzers.GetAnalyzerSemanticDiagnosticsAsync) APIs to compute open file semantic diagnostics. This PR performs the following optimizations on this code path: 1. `AnalysisState.PerAnalyzerState`: Delay allocations of per-symbol dictionary values stored in `_pendingDeclarations` map until we actually start analyzing the first declaration for the symbol. This avoids unncessary allocation overhead on the dictionary pool from which these dictionaries are allocated. 2. `CompilationWithAnalyzers` and `AnalyzerDriver`: Ensure that we force complete partial type trees only for symbol start analyzer(s) in the original analysis scope for which diagnostics were requested. Our current logic force completed partial tree diagnostics for all analyzers if at least one of the analyzer is a symbol start analyzer, which is always true as IDE already has few symbol start analyzers. Addresses VSO [#922802](https://dev.azure.com/devdiv/DevDiv/_workitems/edit/922802) and [#922837](https://dev.azure.com/devdiv/DevDiv/_workitems/edit/922837)
-
- 17 7月, 2019 4 次提交
-
-
由 Charles Stoner 提交于
-
由 Fred Silberberg 提交于
Adds a public API, `NullableContext GetNullableContext(int position)`, for determining the nullable context at a particular file location, and types supporting that API.
-
由 Tomáš Matoušek 提交于
* Fix EnC debug information emitted for patterns Update calculation of syntax offset to account for a new case when a node (a switch expression) that is associated with a variable, closure or lambda may share start offset with other node of the same kind (`expr switch { … } switch { … }`). Use the offset of the `switch` keyword instead of the starting offset of the expression to disambiguate. Assign ordinals to variables synthesized for storing pattern values across cases. This is required to support complex patterns since we can no longer rely on the type of these variables to be distinct. This will require follow up in the IDE to disallow updating/adding/reordering the case clauses of switch expression which there an active statement is present within the switch statement. If the cases are unmodified the compiler guarantees that the order in which the synthesized variables are generated remains the same, so we can map the variables using their ordinal. Mark all variables synthesized during lowering of switch expression as short-lived. Their lifespan is limited to the switch expression, which does not include a sequence point. Disallow editing methods that contain switch expression. This is necessary until bugs https://github.com/dotnet/roslyn/issues/37232, https://github.com/dotnet/roslyn/issues/37237 are fixed. * Feedback * Update tests
-
由 Andy Gocke 提交于
Will be consumed by tooling to recommend LangVersion
-
- 16 7月, 2019 3 次提交
-
-
由 Julien Couvreur 提交于
-
由 Julien Couvreur 提交于
-
由 Fred Kleuver 提交于
-
- 13 7月, 2019 3 次提交
-
-
由 Julien Couvreur 提交于
-
由 Andy Gocke 提交于
Fixes #29819
-
由 Tomáš Matoušek 提交于
* Top-level types enumeration refactoring * Simplify DefinitionMap * Include namespaces in synthesized definition map * Add SynthesizedNamespaceSymbol * Embedded Attributes * Test synthesized attributes * Clean up EnC tests * Clean up symbol matcher tests * Ref readonly return type, in parameter symbol matching tests * Enable using ref readonly returns, in parameters, ref structs during debugging * More tests * ReadOnly struct members * Fix langauge version mismatch * Merge fix ups * Feedback, skip tests
-
- 12 7月, 2019 2 次提交
-
-
由 Charles Stoner 提交于
-
由 Fredric Silberberg 提交于
-
- 11 7月, 2019 1 次提交
-
-
由 Jason Malinowski 提交于
-
- 10 7月, 2019 2 次提交
-
-
由 Andy De George 提交于
-
由 Julien Couvreur 提交于
-
- 06 7月, 2019 1 次提交
-
-
由 Rikki Gibson 提交于
-
- 04 7月, 2019 1 次提交
-
-
由 Neal Gafter 提交于
-
- 02 7月, 2019 2 次提交
-
-
由 Rikki Gibson 提交于
-
由 Neal Gafter 提交于
Fixes #35843
-
- 29 6月, 2019 4 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 28 6月, 2019 3 次提交
-
-
由 Kirill Osenkov 提交于
When a .ruleset file includes a non-existing ruleset reference we receive null from ResolveIncludePath and throw a FileNotFoundException, which is the immediately caught in LoadRuleSet. We can avoid the first-chance exception and the associated allocations if we just return null. A missing ruleset is not an exceptional situation so no need to use exceptions for control flow here if we can avoid it.
-
由 Fredric Silberberg 提交于
-
由 Fredric Silberberg 提交于
-
- 26 6月, 2019 3 次提交
-
-
由 Petr Houška 提交于
-
由 Charles Stoner 提交于
-
由 Rikki Gibson 提交于
-
- 21 6月, 2019 3 次提交
-
-
由 Ivan Basov 提交于
-
由 Jason Malinowski 提交于
The code style settings we already had in a .editorconfig file supplied a set of terms to set different diagnostic severities. The terms don't match the underlying compiler enum, but we will adopt them for setting compiler diagnostic settings as well to keep the values consistent inside a .editorconfig file. Fixes https://github.com/dotnet/roslyn/issues/35690
-
由 Manish Vasani 提交于
-
- 20 6月, 2019 1 次提交
-
-
由 Manish Vasani 提交于
-