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

Standardize "images" and the rune-runtime interface #185

Open
Michael-F-Bryan opened this issue May 28, 2021 · 0 comments
Open

Standardize "images" and the rune-runtime interface #185

Michael-F-Bryan opened this issue May 28, 2021 · 0 comments
Labels
area - runtime The Rust Rune runtime category - enhancement New feature or request effort - hard This should be pretty simple to fix

Comments

@Michael-F-Bryan
Copy link
Contributor

At the moment, the interface between a Rune and its runtime (the "image") is defined in a single extern "C" block with host bindings being wired up manually by the runtime implementation.

If we want to make it easier for defining runtimes or create new capabilities and model backends, we'll need to create an easy, standardised way to define images.

This will probably also require bytecodealliance/wasmtime#2949.

@Michael-F-Bryan Michael-F-Bryan added category - enhancement New feature or request effort - hard This should be pretty simple to fix area - runtime The Rust Rune runtime labels May 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area - runtime The Rust Rune runtime category - enhancement New feature or request effort - hard This should be pretty simple to fix
Projects
None yet
Development

No branches or pull requests

1 participant