- 12 9月, 2019 1 次提交
-
-
由 Joey Robichaud 提交于
-
- 10 9月, 2019 2 次提交
-
-
由 Fred Silberberg 提交于
Run scripts/PublicAPI/mark-shipped.cmd
-
由 Fredric Silberberg 提交于
-
- 04 9月, 2019 2 次提交
-
-
由 Manish Vasani 提交于
Move to a newer FlowAnalysis utilities package
-
由 Fred Silberberg 提交于
Support building the workspaces layer in source-build
-
- 01 9月, 2019 1 次提交
-
-
由 Manish Vasani 提交于
This addresses the memory leak in #38330. The underlying memory leak was fixed in the FlowAnalysis utilities assembly with https://github.com/dotnet/roslyn-analyzers/pull/2795. This PR just moves to newer Roslyn Flow analysis utilities package reference with the fix. Fixes #38330
-
- 31 8月, 2019 7 次提交
-
-
由 Fredric Silberberg 提交于
-
由 Fredric Silberberg 提交于
-
由 Fredric Silberberg 提交于
Condition targets that use InitializeSourceControlInformation on whether or not that target is available.
-
由 Fredric Silberberg 提交于
-
由 Fredric Silberberg 提交于
-
由 Fredric Silberberg 提交于
Support building the workspaces layer in source-build. Also added a verification step to CI to ensure we don't break the build.
-
由 Charles Stoner 提交于
Port the fix for #38183 to 16.3.
-
- 29 8月, 2019 3 次提交
-
-
由 vatsalyaagrawal 提交于
Do not report an NFW for analyzer exception diagnostic in IDE
-
由 Jason Malinowski 提交于
Wire-up to text buffers even if there is no RDT DocDataReloaded
-
由 Jason Malinowski 提交于
In 735a6532 we stopped listening to RDTA_DocumentInitialized as a trigger to know when the document might now be available. We believed it wasn't necessary since DocDataReloaded would cover it, but files being opened or manipulated via some DTE interfaces or with the invisible editor seem to still require it. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/937712
-
- 28 8月, 2019 2 次提交
-
-
由 Joey Robichaud 提交于
-
由 AlekseyTs 提交于
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/797080. We have several Watson buckets that imply that a TypeWithAnnotations structure returned by RetargetingMethodSymbol.ReturnTypeWithAnnotations and RetargetingPropertySymbol.TypeWithAnnotations has null as its Type property. The properties are backed by fields that are initialized by an API that never produces structures like that (with null Type property). I suspect that the situation can arise in case of a race between two threads, where the structure is only partially initialized so that IsDefault check fails in one thread, but the underlying information for the Type property is still not initialized by another thread. This change eliminates possibility of races like that. Related to #38247.
-
- 27 8月, 2019 1 次提交
-
-
由 Manish Vasani 提交于
-
- 25 8月, 2019 1 次提交
-
-
由 Neal Gafter 提交于
Before C# 8, the reduction of an extension method would fail (return null) when the method's constraints would not be satisfied. But in C# 8 the unmanaged constraint requires we know the language version, and therefore the compilation, to check. That is not available in `IMethodSymbol.ReduceExtensionMethod`. So we dropped the constraint checking in #37022. However this causes an unfortunate regression in the quality of the IDE experience. So here we restore the constraint checking, using the compilation's language version when available. IMethodSymbol.ReduceExtensionMethod uses the C# 8 rules since it has no language version to check. Fixes #37780
-
- 24 8月, 2019 1 次提交
-
-
由 dotnet-automerge-bot 提交于
Merge release/dev16.3-preview2 to release/dev16.3
-
- 23 8月, 2019 2 次提交
-
-
由 Manish Vasani 提交于
This seems to cause a noticable UI delay while the NFW gets reported. We already report the AD0001 diagnostic with exception callstack and the analysis context on which exception occurred, so user has enough information to file an actionable bug. Fixes #38180
-
由 Andy Gocke 提交于
Merge remote-tracking branch 'upstream/release/dev16.3-preview2' into merges/release/dev16.3-preview2-to-release/dev16.3
-
- 22 8月, 2019 6 次提交
-
-
由 Andrew Hall 提交于
Extract method will now maintain nullable reference types for parameters and return types. If the parameters or return types are determined to be non-nullable through flow state analysis, then we will adjust them to be non-null when generating. For return type, the adjustment is done after the method is generated. This is because the generator can and will introduce new return statements that need to be analyzed for null state. The only way a return type can be modified to non null is if it: 1. Was null annotated to start with 2. All returns are determined to return non-null by flow state analysis. Similarly, reference parameters can be assigned null or non-null values inside a method. We determine parameters can be adjusted if: 1. Null is not passed into the parameter. 2. Null is never assigned to the parameter.
-
由 Joey Robichaud 提交于
Remove the 7.3 languageversion from the BindSymbolInOtherFile test
-
由 Manish Vasani 提交于
Handle escaping of ref/out parameters on non-regular CFG exit paths (…
-
由 Joey Robichaud 提交于
-
由 Andy Gocke 提交于
-
由 Jason Malinowski 提交于
Remove inaccessible attributes when generating code
-
- 21 8月, 2019 11 次提交
-
-
由 Jason Malinowski 提交于
Show nullable annotations in tuple signature help
-
由 Jason Malinowski 提交于
Update Generate Equals and GetHashCode to handle nullable members
-
由 Andrew Hall 提交于
-
由 Joey Robichaud 提交于
Do not fade code for IDE0016 (UseThrowExpressionDiagnosticId)
-
由 Manish Vasani 提交于
Revert test workarounds/skip for IDE diagnostic configuration code fixes
-
https://github.com/dotnet/arcade由 dotnet-maestro[bot] 提交于
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19419.12
-
由 Andy Gocke 提交于
Merge release/dev16.2 to release/dev16.3-preview2
-
由 Jason Malinowski 提交于
Most of the tests in here still hard code older baselines because they predate some pattern matching improvements, but this is fully new.
-
-
由 Jason Malinowski 提交于
Fix generated Equals(object) parameter nullability mismatch
-
-