fix: reexport async_trait::async_trait

[tamaroning]

This PR

To create a new provider using this library, we need to use the #[async_trait] macro to impl traits.

Related Issues

Notes

Follow-up Tasks

none

How to test

none

[tamaroning]

Can someone rerun CI?

[tamaroning]

Oh thank you. It complained about the title of this pr.

[beeme1mr]

Oh thank you. It complained about the title of this pr.

It should be fixed now.

[sheepduke]

Just one question: is it required to export that?

I mean, is it technically required, or does it lead to a better design?
(I thought the user could directly import async_trait to achieve this, but it might be ugly...)

[tamaroning]

I tried to impl FeatureProvider without #[async_trait] but couldn't because this macro seems to generate complex lifetime annotations so using the async_trait macro is probabley required.
If this library does not export the macro, users have to import async_trait on their own and make sure that its version matches with this repo. (it will be ugly)

Async-rust, a famous graphql implementation in Rust, for example, export async_trait in this line.

[sheepduke]

I tried to impl FeatureProvider without #[async_trait] but couldn't because this macro seems to generate complex lifetime annotations so using the async_trait macro is probabley required. If this library does not export the macro, users have to import async_trait on their own and make sure that its version matches with this repo. (it will be ugly)

Async-rust, a famous graphql implementation in Rust, for example, export async_trait in this line.

Thanks for educating me! Now I totally understand it.