Enable explicit nulls in community build #23948
Draft
Conversation
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
HarrisL2
force-pushed
the
explicit-nulls-communitybuild
branch
3 times, most recently
from
ac7addc to
9bb292a
Compare
HarrisL2
force-pushed
the
explicit-nulls-communitybuild
branch
3 times, most recently
from
77e303a to
dd9fef9
Compare
HarrisL2
force-pushed
the
explicit-nulls-communitybuild
branch
from
150ecfc to
13e7bae
Compare
HarrisL2
force-pushed
the
explicit-nulls-communitybuild
branch
from
13e7bae to
604fa53
Compare
HarrisL2
force-pushed
the
explicit-nulls-communitybuild
branch
from
604fa53 to
d8102c5
Compare
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 PR tries to enable -Yexplicit-nulls in the community build, and makes changes in the community to get the code to compile.
A mirror of this without -Yflexify-tasty is available at #24099