- 14 2月, 2020 1 次提交
-
-
由 Charles Stoner 提交于
-
- 02 2月, 2020 1 次提交
-
-
由 Charles Stoner 提交于
-
- 23 1月, 2020 1 次提交
-
-
由 Jonathon Marolf 提交于
-
- 04 1月, 2020 1 次提交
-
-
由 Neal Gafter 提交于
Fixes #40197
-
- 18 12月, 2019 1 次提交
-
-
由 Julien Couvreur 提交于
* Refactor tuple implementation * Tweaks * Address PR feedback * Pass tuple data in constructors * Address more feedback * Tweak comparison * Restore constructWithTypeParameters flag to avoid overflow * Assert that tuple parameter matches TupleUnderlyingType somewhat * Rename to TupleData. Address some IDE feedback * Remaining TODO2's * Fix last IDE test! * Factor array comparison * Tweak WithTupleData and EqualsIgnoringTupleUnderlyingType * Expand a test * Remove duplicate line * Remove an EE test for badly formed ValueTuple type * PR feedback from Neal * Restore an IDE test without ValueTuple * Rename constants * Restore formatting
-
- 14 12月, 2019 1 次提交
-
-
由 Charles Stoner 提交于
-
- 10 12月, 2019 1 次提交
-
-
由 Charles Stoner 提交于
-
- 04 12月, 2019 2 次提交
-
-
由 Neal Gafter 提交于
Fixes #39767
-
由 Neal Gafter 提交于
Fixes #39947
-
- 02 11月, 2019 1 次提交
-
-
由 AlekseyTs 提交于
This change also separates implementation of ISymbol interfaces from internal symbols in C# compiler.
-
- 15 10月, 2019 1 次提交
-
-
由 Neal Gafter 提交于
Fixes #30669
-
- 26 9月, 2019 1 次提交
-
-
由 Julien Couvreur 提交于
* x == default is valid object equality for reference types * Block null == default
-
- 25 9月, 2019 1 次提交
-
-
由 Gen Lu 提交于
-
- 06 9月, 2019 1 次提交
-
-
由 Julien Couvreur 提交于
-
- 04 9月, 2019 1 次提交
-
-
由 Julien Couvreur 提交于
-
- 25 8月, 2019 2 次提交
-
-
由 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
-
由 Julien Couvreur 提交于
-
- 07 8月, 2019 1 次提交
-
-
由 Nikolay 提交于
-
- 30 7月, 2019 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 16 7月, 2019 2 次提交
-
-
由 Andy Gocke 提交于
Fixes #37187
-
由 Neal Gafter 提交于
Implements https://github.com/dotnet/csharplang/issues/2389 Fixes #35958 Note that the switch expression conversion is not a standard implicit conversion. Specifically, it should not be considered as a valid implicit conversion as input to a user-defined conversion, as that could permit two chained user-defined conversions. Also changes binding of switch expression to ECMA so it can interact properly with switch expressions. Fixes #14965
-
- 25 6月, 2019 1 次提交
-
-
由 yair halberstadt 提交于
-
- 15 6月, 2019 1 次提交
-
-
由 Charles Stoner 提交于
-
- 25 5月, 2019 1 次提交
-
-
由 Andrew Hall 提交于
-
- 22 5月, 2019 1 次提交
-
-
由 yair halberstadt 提交于
-
- 21 5月, 2019 2 次提交
-
-
由 yair halberstadt 提交于
-
由 Charles Stoner 提交于
-
- 15 5月, 2019 1 次提交
-
-
由 Charles Stoner 提交于
-
- 08 5月, 2019 1 次提交
-
-
由 Julien Couvreur 提交于
-
- 07 5月, 2019 1 次提交
-
-
由 Rikki Gibson 提交于
* Add reproducer for #34872 * Fix bug and add test * WIP * Test similar scenario in VB * Add void check in ClassifyConversionFromType, update tuple tests * Cleanup
-
- 04 5月, 2019 2 次提交
-
-
由 Andy Gocke 提交于
Implements a design change where overrides are allowed to change the type of the member as long as there is an implicit nullable reference conversion from the overriding type to the overridden type according to the nullable variance rules. Fixes #23268 Fixes #30958
-
由 AlekseyTs 提交于
Closes #28834. Closes #30061.
-
- 02 5月, 2019 1 次提交
-
-
由 Neal Gafter 提交于
* Permit stackalloc in nested contexts. (#28969) Fixes #26759
-
- 01 5月, 2019 1 次提交
-
-
由 Neal Gafter 提交于
Fixes #29956 Also introduce a helper `TypeSymbol.IsVoidType()`
-
- 30 4月, 2019 1 次提交
-
-
由 AlekseyTs 提交于
Make sure nullability mismatch in constraints specified in different partial declarations (types/methods) are properly detected and reported. (#35272) Make sure nullability mismatch in constraints specified in different partial declarations (types/methods) are properly detected and reported. Fixes #30229. Fixes #35179. Implements the following LDM decision: For partial types, the invariant matching from type inference and merging. A mismatch between two non-oblivious candidates produces an error. No warnings are produced. For partial methods, nullability has to match with exception for oblivious and we produce warnings. For the result, we use the implementation signature inside the implementation, and the declaration signature for the callers.
-
- 12 4月, 2019 1 次提交
-
-
由 Neal Gafter 提交于
Fixes #34233
-
- 06 4月, 2019 1 次提交
-
-
由 Neal Gafter 提交于
-
- 29 3月, 2019 1 次提交
-
-
由 AlekseyTs 提交于
-
- 27 3月, 2019 1 次提交
-
-
由 Julien Couvreur 提交于
Track l-values in conditional operator Assignment to ref variable produces safety warnings
-
- 22 3月, 2019 1 次提交
-
-
由 Neal Gafter 提交于
Fixes #30987
-