Skip to content
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

EIP-001: Specify the calling convention and memory lookup for plugin IO #1

Closed
nilslice opened this issue Aug 5, 2022 · 2 comments
Closed
Labels
EIP Submission and tracking of a new EIP

Comments

@nilslice
Copy link
Member

nilslice commented Aug 5, 2022

@zshipko, I've set up a EIP-001 doc in main to work off of for this spec!

@nilslice nilslice added the EIP Submission and tracking of a new EIP label Aug 5, 2022
@zshipko
Copy link
Contributor

zshipko commented Aug 6, 2022

I added some initial ideas after our discussion, I will probably make some changes next week but it's been updated some thoughts about the direction we could take it in.

@nilslice
Copy link
Member Author

nilslice commented Aug 8, 2022

That looks great! After looking through usage of the Table API, it seemed like maybe we were going to have to force it a bit and comparatively, the Global API seems to be more fitting.

I think it would be possible to hide the details of any mutable global from the plugin author, since they would only be calling wrapped external functions for the offset/length calls. But from the examples in the Global docs, I'm not certain... namely the linking done to provide access to the values within the module from the host.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EIP Submission and tracking of a new EIP
Projects
None yet
Development

No branches or pull requests

2 participants