Peter Huene

That definitely is a bug in `wit-component` (or, more likely, how `cargo-component` is synthesizing the target world by merging in the other component's world). I'll take a look at that...

The panic above is caused by an incorrect world definition created by `cargo-component` for component dependencies that import types. I've put up #121 to address that issue. I'll leave this...

`comp1.wasm` shouldn't need to be rebuilt, the problem lies with how `comp2` was generating its bindings information off of the information in `comp1.wasm`. If you want to use `newgyu:comp1` as...

> I think I didn't identify the difference between component.dependencies and component.target.dependencies. I didn't also get the term of target in this cargo-component context correctly. I'm sorry that my lack...

I just ran into this bug. As far as I can tell, there's no way to determine the original type intention (i.e. was the value quoted?) to prevent strings that...

A `quoted` member would be sufficient for my purposes, at least.

@jbeder Looks like using `Tag` will be a suitable work around for my issue. Thanks for the information!