fix nil
literal giving itself type untyped
/typed
[backport]
#24165
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #24164, regression from #20091
The expression
nil
as the default value of template parameterx: untyped
is typechecked with expected typeuntyped
since #20091. The expected type is checked if it matches thenil
literal with a match better than a subtype match, and the type is set to it if it does. Howeveruntyped
matches with a generic match which is better, so thenil
literal has typeuntyped
. This breaks type matching for the literal. So if the expected type isuntyped
ortyped
, it is now ignored and thenil
literal just has thenil
type.