Closed
Conversation
enricozb
changed the title
Lookup ext vals
enricozb
force-pushed
the
enricozb/lookup
branch
2 times, most recently
from
e1c09d4 to
58c12c9
Compare
enricozb
force-pushed
the
enricozb/lookup
branch
from
58c12c9 to
628ba3a
Compare
Member
|
integrated into #545 |
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
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.
resolves: #460
Branch nodes are now represented as extrinsic function calls. Specifically,
?(b_0 .. b_i c)becomes@branch(?[b_0 .. b_i] c), where?[..]is a lookup extrinsic value. This thus removes the need for theTag::Branchvariant.Lookup extrinsic values can be directly created with the syntax
?[a b .. n], wherea b .. nare all nilary and trivially-copyable nodes (lookup nodes also satisfy this).