-
Notifications
You must be signed in to change notification settings - Fork 89
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
Opaque foreign values #1909
Labels
Comments
Merged
I would close this, given #1931 has been merged. Foreign value are still quite bare-bone, but if there is demand for missing features, I think they would be better handled by new, focused issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is some kind of baby step towards FFI: allow for opaque foreign values to be injected into nickel and copied around, but not otherwise interacted with or modified from within nickel.
This was a request from the keystone project, with some discussion on the discord.
Question: what should be payload of the opaque foreign values be?
u64
might be sufficient: that gives a lot of values, and the user could "embed" richer data by maintaining a lookup table on their side. MaybeBox<dyn Any>
is also a possibility?The text was updated successfully, but these errors were encountered: