- 10 6月, 2020 18 次提交
-
-
由 Sam Harwell 提交于
Update smart token formatter tests for top-level statements
-
由 msftbot[bot] 提交于
Correctly error in function pointer scenarios:
-
由 Sam Harwell 提交于
Update "Move declaration near reference" for top-level statements
-
由 msftbot[bot] 提交于
Allow rename file even if rename was no initiated in that file
-
由 David Poeschl 提交于
Change Signature DataGrid accessibility when navigating cells with CAPS+Arrow
-
由 David Poeschl 提交于
Remove `GetPositionBeforeParameterListClosingBrace` from Change Signature
-
由 Allison Chou 提交于
Fix for selected item jumps out of view with long argument list in Change Signature
-
由 msftbot[bot] 提交于
Merge release/dev16.7-preview3 to master
-
由 Sam Harwell 提交于
Cleaner generated code
-
由 Fredric Silberberg 提交于
-
由 Andrew Hall (METAL) 提交于
-
由 David Poeschl 提交于
-
由 Andrew Hall (METAL) 提交于
-
由 Manish Vasani 提交于
Bump up the version of Microsoft.CodeAnalysis.AnalyzerUtilities
-
-
由 Fredric Silberberg 提交于
-
由 Sam Harwell 提交于
🧹 Code cleanup in CSharpMakeStructFieldsWritableDiagnosticAnalyzer
-
由 Sam Harwell 提交于
-
- 09 6月, 2020 21 次提交
-
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
由 Rikki Gibson 提交于
-
由 Manish Vasani 提交于
-
由 msftbot[bot] 提交于
Merge release/dev16.7-preview3 to master
-
由 Gen Lu 提交于
Switch to consume data from central optprof run
-
由 Chris Sienkiewicz 提交于
* Implement 'GlobalOptions' for analyzer configs, to get global options without a tree or additional file. * Make generator driver take in an AnalyzerConfigOptionsProvider * Refactor where the generators run * Factor out test generators to be shared across test projects
-
由 Tomáš Matoušek 提交于
* Compiler Options in PDB fixups * Use MetadataVisualizerOptions.NoHeapReferences * Add doc back
-
由 Sam Harwell 提交于
Avoid localizing Empty.resx
-
由 Fredric Silberberg 提交于
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
Update dotnet-format to 4.0.130203 Update Microsoft.CodeAnalysis.CodeStyle to 3.7.0-3.20271.4
-
由 Julien Couvreur 提交于
-
由 Julien Couvreur 提交于
-
由 Fredric Silberberg 提交于
-
由 Andy Gocke 提交于
* Emit Clone methods in abstract records as abstract The clone method is designed to call the containing type's constructor, but this can't be done when the containing type is abstract. A reasonable alternative is to make the method abstract. Fixes #44890 * Add test for abstract record in the middle
-
由 Fredric Silberberg 提交于
* When a static type is used as a parameter or return type. * When a restricted type is used as a parameter or return type.
-
由 Manish Vasani 提交于
Dogfood the new .NET analyzers NuGet package
-
由 Kevin Sun 提交于
* Added Error 8053 * Requested PR Changes * Update StructsTests.cs * Update src/Compilers/CSharp/Test/Semantic/Semantics/StructsTests.cs Co-authored-by: NRikki Gibson <rikkigibson@gmail.com> Co-authored-by: NRikki Gibson <rikkigibson@gmail.com>
-
由 Julien Couvreur 提交于
-
- 08 6月, 2020 1 次提交
-
-
由 Manish Vasani 提交于
Roslyn repo currently includes analyzer package references to sub-packages of FxCopAnalyzers package (Microsoft.CodeQuality.Analyzers and Microsoft.NetCore.Analyzers). Due to the high noise level for default enabled CA rules from these packages, we end up turning off majority of these rules for the repo in our ruleset files. This change switches the repo from FxCop analyzers package to .NET analyzers package (NOTE: we plan to ship the analyzer assemblies from this package in the .NET SDK soon). This helps us dogfood the experience from this new analyzer package, especially from the perspective of noise from default enabled analyzers, while also cleaning up our configuration files. Some more details below: - The new package has the same set of CA rules, but the legacy ones are now disabled by default. - There are a handful of rules which are enabled by default as IDE suggestions (Info severity): either as part of the triage of pre-existing CA rules OR recently added by the .NET runtime team. - There are even fewer set of rules which are enabled by default as warnings – all of these have been added by the .NET runtime team, none of the pre-existing rules are enabled as warnings in this package. The core dogfooding aspect would be: 1. Enabled by default rules: 1. Analyzer exception diagnostics (AD0001): absolute must to fix or disable these rules by default in the package. 2. Noise from false positives: It would be a higher priority issue if the false positives are from a rule which is enabled as a build warning, but we should fix even false positives from info rules. We may also want to consider bumping these rules to lower severity or disabling them by default. 3. Rules which had to be turned off for specific projects, say test projects. We should re-triage such rules and consider if they should be disabled by default. 2. Disabled/Info rules which were escalated to Info/Warnings as we found these to be valuable and reliable: We can potentially re-triage each of these rules and consider if they are valuable enough to have its default severity/enabled state changed to benefit customers.
-