Specification of the built-in value type and functions#7810
Open
kwxm wants to merge 8 commits into
Open
Conversation
kwxm
added
Specification
Builtins
No Changelog Required
Contributor
Author
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
1 participant
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 updates the UPLC specification to include the
valuetype and builtins. I've attached a rendered PDF: the main things to look at are Section 4.3.6, in particular 4.3.6.3 and 4.6.3.4 (from page 50 onwards) and the flat encoding in Appendix C (pp 73/74). There's also a CBOR encoding forvaluebut I haven't added that because we won't need it until we add avaluefield todata. The parser is currently more permissive than what's described here, but I'll fix that shortly.We also need to specify casing on constants and update the section on versions (PV/LL etc). I'll do those in separate PRs.
plutus-core-specification.pdf