Skip to content

Middle end/backend/runtime changes for or_null #2532

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

Closed
wants to merge 3 commits into from

Conversation

mshinwell
Copy link
Collaborator

To be described later; this is mainly here so @dkalinichenko-js can work from it. The Lambda interface should be about right.

@mshinwell mshinwell added the or_null Related to or_null layouts label May 3, 2024
@mshinwell mshinwell marked this pull request as draft May 3, 2024 13:50
@mshinwell
Copy link
Collaborator Author

@dkalinichenko-js I've just added some more commentary in lambda.mli which will hopefully be of use.

@@ -737,6 +737,8 @@ let rec layout_union l1 l2 =
match l1, l2 with
| Pbottom, l
| l, Pbottom -> l
| Pnullable_value value_kind1, Pnullable_value value_kind2 ->
Pnullable_value (value_kind_union value_kind1 value_kind2)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we also want a join between Pnullable_value and Pvalue to return something better than Ptop? This is necessary if the layouts are not incompatible.

@dkalinichenko-js
Copy link
Contributor

With #2614 merged, we should be able to connect this to the front-end.

@mshinwell
Copy link
Collaborator Author

Superceded by newer PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
or_null Related to or_null layouts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants