-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow importing Cryptol foreign
functions
#1920
Conversation
to access cryptol implementations of foreign functions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @qsctr! Aside from the comments below, it would be worth mentioning this in the CHANGES.md
file and the SAW manual (under doc/manual
), as this is a user-facing feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
If there exists a Cryptol implementation of the
foreign
function, then we import it into SAWCore as a Cryptol expression, in the same way that we do for normal Cryptol bindings. If not, then we introduce it as an opaque constant with no definition, the same way we deal with unknown primitives.This requires an update of the
cryptol
submodule so that we have support for Cryptol implementations offoreign
functions.