Fix comparing AnyVal | Null to Null and selecting in UnsafeNulls #13837
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.
When typing a Select under unsafeNulls, we should only strip
Null
fromT | Null
ifT <:< ObjectType
, so that unsafeNulls will have same behaviours as regular scala without explicit nulls.This PR fixs comparing
AnyVal | Null
withNull
using==
and!=
in unsafeNulls:It also disallows selecting members of
AnyVal
onAnyVal | Null
: