RFC: Re-export zbus_derive macro in zbus for convenience
Since we're going for the macros as our recommended API, it makes sense to re-export the zbus_derive
macros in zbus for convenience. It should still be optional though, through a feature (like serde does with its derive
feature).
This is a follow-up discussion from !112 (merged):
-
@zeenix started a discussion: (+2 comments) I've not yet seen any crate that provides macros as it's main API but rather macros are always additional magic on the top that makes things super easy. The practice of keeping macros in a separate crate on top, also is in line with that.
So I think we should highly recommend people to use the easier derive macros but not discourage people from using the manual API w/o macros. i-e macro usage should be optional.
There could always be issues with macro magic and users should have a stable-enough way to workaround it by using manual API (at least until the issue with macro is fixed and they can bump their dep on the new version of zbus_derive).