Change Untyped from Null to Nothing for Trees #13883
Merged
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.
Untyped = Nothing
is a more logical choise forTrees
, since an untyped tree should not have any value for its type.This change will also make migration to explicit-nulls more easy (the type bound
Untyped <:< Type
becomes valid).I don't notice any compiling error after I change the definition of
Untyped
type, so I guess the inference issue mentioned in the comment has been solved? @odersky