Wasmtime GitHub notifications bot (Aug 30 2023 at 19:23): Wasmtime GitHub notifications bot (Aug 30 2023 at 19:23):Kylebrown9 commented on issue #6936:
I think I heard there was a component macro, looked in the
wasmtime/cratesfolder, found it, and wasn't at all clear that this was re-exported somewhere else. It's also independently available on crates.io so I figured it was the right thing/place but really poorly documented.
Wasmtime GitHub notifications bot (Aug 30 2023 at 19:23):Kylebrown9 edited a comment on issue #6936:
I think I heard there was a component macro, looked in the
wasmtime/cratesfolder, found it, and wasn't at all clear that this was re-exported somewhere else. It's also independently available on crates.io so I figured it was the right thing/place but really poorly documented.I've been using it for months in my template compiler tests and nobody whose looked at it noticed it was wrong either.
Wasmtime GitHub notifications bot (Aug 30 2023 at 19:44):Kylebrown9 edited issue #6936:
The arguments are not documented and the only way to figure out what they are easily is to dig through the arguments parsing source.
The possible arguments and common combinations of them should be documented in the README for
wasmtime_component_macro.
Wasmtime GitHub notifications bot (Aug 30 2023 at 20:05):alexcrichton commented on issue #6936:
Oh interesting! What led you to use
wasmtime-component-macrodirectly? That in theory should be an internal crate that no one uses, so our documentation shouldn't ever have that in there.
Last updated: Nov 22 2024 at 17:03 UTC