- 13 3月, 2019 7 次提交
-
-
由 Neal Gafter 提交于
-
-
由 Neal Gafter 提交于
e.g. `ReturnType`, `ElementType`, etc.
-
由 Neal Gafter 提交于
-
由 Andy Gocke 提交于
Ref and out parameters with suppression should change the nullable state for the argument being suppressed. Moreover, the changes should flow through type inference. Closes #27743
-
由 Jared Parsons 提交于
Fix local bootstrap build
-
由 dotnet-automerge-bot 提交于
Merge dev16.0 to master
-
- 12 3月, 2019 17 次提交
-
-
由 Julien Couvreur 提交于
-
由 Joey Robichaud 提交于
Merge dev16.0 to master
-
由 Julien Couvreur 提交于
-
由 Jared Parsons 提交于
Have to disable quiet restore explicitly on local dev machines when doing a bootstrap build to work around this arcade issue: https://github.com/dotnet/arcade/issues/2220
-
由 Vladimir Sadov 提交于
Check nullness of a nullable receiver when invoking base methods.
-
由 Jared Parsons 提交于
Fix stack overflow compiling deeply nested generic
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Andy Gocke 提交于
-
由 Vladimir Sadov 提交于
Nullable nontrivial constructor should propagate state of the argument to Value.
-
由 Neal Gafter 提交于
* Correct parsing of a parenthesized constant pattern expression in switch expression arm Fixes #33675 * Add a test that we properly bind and code-gen a parenthesized constant expression.
-
由 Gen Lu 提交于
handle extension methods in "Sync Namespace" refactoring
-
由 Jared Parsons 提交于
Did some profiling and all of the slowness is due to peverify. It seems to hit a wall about 700 levels of nesting. Once it's removed we can easily test our tolerance levels in the compiler
-
由 vsadov 提交于
-
由 Neal Gafter 提交于
* Implement LDM decisions on the behavior of `??` and `??=` operators Fixes #33743
-
由 Tomáš Matoušek 提交于
* Update CoreFX dependencies * Generate suggested binding redirects
-
由 Sam Harwell 提交于
Wait for graceful close before terminating process
-
- 11 3月, 2019 5 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
As a part of implementing nullable reference types many of our locals switched from `TypeSymbol` to `TypeSymbolWithAnnotations`. In the vast majority of cases this doesn't have a meaningful impact on compilation. They are bigger (about 3X) but it's still a relatively small `struct` (three words). The size difference is significant though in `BindNamespaceOrTypeOrAliasSymbol`. This method is used in recursive parts of binding and is mutually recursive with `BindQualifiedNam`. This method defines a large number of locals which contribute to every layer of recursion. When they moved to `TypeSymbolWithAnnotations` this pushed us outside our tolerance levels and we hit an overflow in extreme cases. Virtually none of these locals are used in the recursive case. Factored their use into local functions so we only pay the stack usage on demand. closes #33909 fixes https://github.com/dotnet/coreclr/issues/22757
-
- 09 3月, 2019 11 次提交
-
-
由 Jared Parsons 提交于
Pass NoBuild=true to Publish step
-
由 Tomáš Matoušek 提交于
-
由 Tomas Matousek 提交于
-
由 vsadov 提交于
Bases of Nullable are reference types and thus base methods are called via boxed values which wold NRE on nulls. Fixes:#33174
-
由 Neal Gafter 提交于
-
由 Ivan Basov 提交于
-
由 vsadov 提交于
-
由 Tomáš Matoušek 提交于
-
由 Sam Harwell 提交于
Improve test performance
-
由 Neal Gafter 提交于
- Rename `TypeSymbolWithAnnotations` to `TypeWithAnnotations` - Rename its type field from `TypeSymbol` to `Type` - Fields of Symbols that are of type `TypeWithAnnotations` that are currently named `Type` would be renamed `TypeWithAnnotations` Fixes #33736
-
由 vsadov 提交于
-