- 07 4月, 2018 2 次提交
-
-
由 Julien Couvreur 提交于
-
由 Julien Couvreur 提交于
-
- 06 4月, 2018 18 次提交
-
-
由 Dustin Campbell 提交于
Not offering UseAutoProperty for volatile fields & when field used with ref
-
由 Jonathon Marolf 提交于
Merge dev15.7.x to master
-
由 Šimon Koníček 提交于
-
由 Jonathon Marolf 提交于
-
由 Dustin Campbell 提交于
Adding missing completion after 'ref'
-
由 Dustin Campbell 提交于
Fixing async keyword highlighting on local functions
-
由 Andy Gocke 提交于
While implementing the tests for the ref-reassignment test plan (#22466) I found a bug in the handling of the ref-escape scope of a ref local in foreach. That bug is fixed and the rest of the items in the test plan should have a test. Fixes #22466
-
由 Omar Tawfik 提交于
* Produce errors on invalid pdbpath supplied to compiler * More tests
-
由 Šimon Koníček 提交于
-
由 Andy Gocke 提交于
The scenario listed in https://github.com/dotnet/roslyn/issues/22700 demonstrates the problem. The direct cause of the crash is that local lowering produces two instances of the lambda and lamda conversions in the resulting bound nodes. This crashes the closure conversion pass since the same lambda cannot appear in two places in the tree. However, even if that were allowed, this would violate the language specification. Placing a lambda inside an indexer which is nested in a compound assignment creates two calls which contain the delegate produced by the lambda expression. If the expression kind is marked as side-affecting it will be spilled into a temporary variable. However, the local lowering doesn't distinguish between whether an expression is side-affecting and whether or not it is referentially transparent. In this case, both matter. Since the delegate produced by the conversion can be compared by reference to any other delegate produced by the same lambda, the code must be referentially transparent -- it must produce the same result when evaluated repeatedly. The fix is small: mark lambda conversions as side-affecting. There are certain cases, like the creation of temporaries for out-of-order calls with named parameters, where the lambda conversion is only required to be non-side-affecting instead of referentially transparent, but it does not currently seem worth the implementation effort to split up the code path. Fixes #22700
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Sam Harwell 提交于
Disable flaky test WorkCoordinatorTests.FileFromSameProjectTogetherTest
-
由 Jeff Zhou 提交于
Merged on behalf of @skynetv Thanks
-
由 Alireza Habibi 提交于
-
由 Sam Harwell 提交于
Fixing NullReferenceException inside GenerateTypeCodeFixProvider when System.Action is missing
-
由 Dustin Campbell 提交于
Trivial fix for potential null-ref in test helper
-
由 Dustin Campbell 提交于
Bug fixes in SwitchStatementHighlighter
-
- 05 4月, 2018 20 次提交
-
-
由 Sam Harwell 提交于
See #25931
-
由 Šimon Koníček 提交于
-
由 Šimon Koníček 提交于
-
由 Šimon Koníček 提交于
-
由 Dustin Campbell 提交于
-
由 Šimon Koníček 提交于
-
由 Omar Tawfik 提交于
* Overload Resolution now fails with the correct error * PR Comments * Clean up
-
由 Omar Tawfik 提交于
* Partial methods implementation should match declaration parameter ref kinds * More tests
-
由 Dustin Campbell 提交于
Major MSBuildWorkspace update
-
由 Carol Hu 提交于
use latest language version for Miscellaneous Files workspace
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Manish Vasani 提交于
Add publish data for features/dataflow branch
-
由 Dustin Campbell 提交于
-
由 Omar Tawfik 提交于
-
由 Jason Malinowski 提交于
Merge dev15.7.x to master
-
由 JieCarolHu 提交于
-
由 JieCarolHu 提交于
-
由 Julien Couvreur 提交于
-
由 Jonathon Marolf 提交于
-