Nullness :: Improvement :: Overrides of generic methods with nullable type instantiations #18337
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 #17988
In the object model, overrides for originally nullable slots can narrow the return type from nullable to not-null.
This was added especially in the context of
ToString()
, which is by default nullable, but most common implementation just return string.However, the relaxation from a
Withnull
return type to a nullness inference variable has been done even for generic code, one that has been explicitely instantiated with a nullable type in place forT
.This changes the "nullable relaxation for overrides" to stop applying in the case of generic return types (i.e. it will not attempt to relax those, and instead keep the exact type which was passed in.).