[FEATURE] Null-safe field assign #8
Merged
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
NotHyper-474
commented
Jul 24, 2025
NotHyper-474
force-pushed
the
feat/nullsafe-assign
branch
from
ee46aa8 to
6a6e88a
Compare
|
Oh yeah this isn't really foolproof so don't ever dare doing something like |
NotHyper-474
force-pushed
the
feat/nullsafe-assign
branch
from
2f9d871 to
1fdede2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Basically adds support for doing stuff like
obj?.x = True.... This would grant you a compile error in Haxe 4 but doesn't in 5 so why not 🤷The way it works is that
?.basically becomes a ternary except it assigns the field inside its block.Shoutout to Keoiki for the idea.
