Support nockma scry #2678
Merged
Support nockma scry #2678
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
paulcadman
force-pushed
the
support-nockma-scry
branch
from
08ecfe3 to
0b3c2f1
Compare
paulcadman
force-pushed
the
support-nockma-scry
branch
2 times, most recently
from
2edc12d to
40be37d
Compare
janmasrovira
previously approved these changes
Mar 21, 2024
This builtin calls Anoma/Nockma scry
Co-authored-by: Jan Mas Rovira <janmasrovira@gmail.com>
Apply this transformation to the Tree->Asm translation.
paulcadman
force-pushed
the
support-nockma-scry
branch
from
40be37d to
9020516
Compare
janmasrovira
approved these changes
Mar 21, 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 PR adds support for Anoma/Nockma scry OP. It is used for obtaining values from the Anoma storage (key value store). See the linked issue for details on scry.
This PR adds support for scry to the Nockma language and compilation from the frontend via a builtin:
anoma-get:In the backend, the
ValueandKeytypes could be anything, they will depend on choices of Anoma applications. The type of the returnedValueis unchecked. It's currently the responsibility of the user to match the annotated type with the type of data in storage.We will not put this builtin in the standard library. It will be exposed in the anoma-juvix library. It's likely that the frontend
anomaGetfunction will evolve as we use it to write Anoma applications and learn how they work.