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

Export Wasm globals ? #30

Closed
ljulliar opened this issue Jan 31, 2020 · 4 comments · Fixed by #32
Closed

Export Wasm globals ? #30

ljulliar opened this issue Jan 31, 2020 · 4 comments · Fixed by #32
Assignees
Labels
📦 component-extension About the Ruby extension written in Rust 🎉 enhancement New feature or request

Comments

@ljulliar
Copy link

Hi there,

It is unclear to me whether one can access exported Wasm globals with ruby-ext-wasm. I tried and I got some kind of weird errors when instatiating a wasm module with exported globals like "global must be a const" (although the wasm code was perfectly valid)
Thanks!

@ljulliar ljulliar added the 🎉 enhancement New feature or request label Jan 31, 2020
@Hywan Hywan self-assigned this Feb 5, 2020
@Hywan Hywan added the 📦 component-extension About the Ruby extension written in Rust label Feb 5, 2020
@Hywan
Copy link
Contributor

Hywan commented Feb 5, 2020

I can implement that quickly, as I did for python-ext-wasm in wasmerio/wasmer-python#120. Would it fit your needs?

@ljulliar
Copy link
Author

ljulliar commented Feb 7, 2020 via email

@Hywan
Copy link
Contributor

Hywan commented Feb 7, 2020

See #32 for the Global API.

To answzer your side question: For the moment, no, we need to support polymorphic host functions in Wasmer (the Wasmer runtime) directly. I'm working on it, since it will unblock host functions support in Ruby.

@ljulliar
Copy link
Author

ljulliar commented Feb 15, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 component-extension About the Ruby extension written in Rust 🎉 enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants