Benefit from explicit-nulls in CpIndex and IndexData#313
Draft
ggVGc wants to merge 8 commits into
Draft
Conversation
ggVGc
force-pushed
the
valter/explicit-nulls
branch
from
4f38481 to
a29375e
Compare
ggVGc
force-pushed
the
valter/index-data-non-null
branch
from
49187fa to
4246bda
Compare
ggVGc
commented
Aug 27, 2025
ggVGc
commented
Aug 27, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This builds on #310 and is the first followup change where we remove
import scala.language.unsafeNullsand benefit from explicit null checking.