Conventions for namespaces generated by macros about cargo-component

[peterhuene]

Hi @NewGyu, thanks for the question!

This is a convention that comes from the wit-bindgen crate; the only difference is that cargo_component_bindings::generate! puts all of the bindings into a bindings module rather than where the macro is invoked.

Functions that are directly exported from the world are represented with a "top-level" Guest trait (i.e. bindings::Guest).

Interfaces exported from the world go in the bindings::exports module, where each sub-module is for an interface that is exported (e.g. bindings::exports::component::case0::random).

The exports module differentiates from an import of an interface in the world (e.g. bindings::component::case1::random; in that example, it's imported because of the use).

[NewGyu]

Hello @peterhuene, thank you for the detailed explanation. That was very helpful.

[NewGyu]

Functions that are directly exported from the world are represented with a "top-level" Guest trait (i.e. bindings::Guest).

Just my personal opinion, I think the namespace of the Guest trait should be unified to start with bindings::exports:: even if the world exports "top-level" function.