Add RM low-level interface and high-level to low-level translation #23
Conversation
This file contains 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
This describes the interface exposed by the transparent instantiation of the RM specification.
Most Set operations can be done using the Juvix Set type. The only operations that are required for the Anoma interface are those which translate to/from the Stdlib Set type.
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.
The aim of this PR is to add a low-level Anoma interface which matches the structure of data that must be sent to the node.
The API that application developers use is called the 'high-level' interface. This PR will add a translation layer from the high-level to the low-level interface. The high-level interface can have use richer types and include facilities to improve the developer UX.