-
Notifications
You must be signed in to change notification settings - Fork 57
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
feature request: bindings subcommand #362
Comments
A somewhat lighter-weight alternative that works today is |
This is a slightly bigger change, but what @sunfishcode what do you think about re-introducing a macro to generate the bindings, or a Reading over the previous context it seems like we removed it in order to increase build speed, but it really seems like what we want is to hook into the build process and ensure bindings are built (and if they can't be, to error early/quickly) -- I think in most of the ecosystem outside of I agree with both of you here and want to point out that the experience of
And then found this issue because it doesn't exist (yet!). That made me start to think again about the whole starting experience here. |
Add a `bindings` subcommand, which just generates the bindings.rs file. And make the `new` subcommand auto-generate the bindings.rs file too, so that the tree is fully set up after a `new`. Fixes bytecodealliance#362.
I've now submitted #366 which adds a @vados-cosmonic I also added some code to auto-generate the bindings as part of I'm not opposed to larger changes, but I'm curious if these simple fixes are enough. |
Hey @sunfishcode IMO that's perfect, thanks -- the The README and related documentation should probably be changed to match as well, but I'm in favor of making that a separate, focused issue (so we can capture the parts to change, and maybe even do a bit of a docs overhaul for this crate). |
The new |
When working on a component locally, I often go through this flow:
Currently, afaik, the way to generate the new bindings is to run a full
cargo component build
. This has a few drawbacks:I think it would be a tooling improvement to have an explicit subcommand that just generates the bindings, without building the full component
The text was updated successfully, but these errors were encountered: