-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move or_null
back to beta
#3625
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little disturbed that this doesn't actually change the meaning of any extension in the compiler, but I think it's fine. Just saying this here to make sure you're thinking about this aspect too.
What about re-exports of |
Yep, it's expected that it doesn't change the typechecking or the middle-end. You can't get a null value without using |
Exports won't work either since |
* `or_null` is beta * fix existing or-null tests * `or_null` is not stable * format * fix exports * accept test_iarray_typeopt * more tests * beta universe instead of alpha --------- Co-authored-by: Diana Kalinichenko <[email protected]>
Title. Only add the
or_null
type when layouts are at least beta. Layouts likeany_non_null
orvalue_or_null
are still available, since the bug only happens when working withNull
values incorrectly considered impossible by the simplifier.