-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
Data I/O #45
Comments
Hey @zwass; thank for reaching out. To answer your first question: yes, that is currently the case. In terms of further interop: it's something that is currently being explored. It's very early in terms of thinking, and an API design is not fully understood at this stage. If you are keen to discuss more, or you have ideas you can reach out in Gophers Slack. |
FYI: #50 |
FYI: #59 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can you help me understand if the following interpretations are correct?
The only way to get input data to the script is by printing the data into the script itself.
The only way to get output data is from the stringified value of the result of the script.
Are there plans to add additional ways to share values back and forth between Go and V8?
The text was updated successfully, but these errors were encountered: