Set-theoretic tuple types (using lists) #13752
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
josevalim
reviewed
Aug 1, 2024
josevalim
reviewed
Aug 1, 2024
josevalim
reviewed
Aug 1, 2024
josevalim
reviewed
Aug 1, 2024
josevalim
reviewed
Aug 1, 2024
josevalim
reviewed
Aug 1, 2024
josevalim
reviewed
Aug 1, 2024
|
💚 💙 💜 💛 ❤️ |
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.
This is a rewrite of #13576 that uses lists instead of relying on the map type implementation.
It adds to the Descr fixed-size tuple types such as
{:ok, binary(), integer()}and open tuple types (such as{atom(), boolean(), ...}, which represent every tuple of at least two elements that are an atom and a boolean).Tuples are now encoded as pairs {tag, elements} where element is a list of types.