Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-async support? #3

Open
mripard opened this issue Jun 2, 2022 · 4 comments
Open

Non-async support? #3

mripard opened this issue Jun 2, 2022 · 4 comments

Comments

@mripard
Copy link

mripard commented Jun 2, 2022

Hi,

Thanks for publishing this crate and all the other, related, ones.

I'd like to use it in a small program that wouldn't use async or tokio, and it's not clear to me whether it can be done.

The doc says:

Full async (requires Tokio).

which is a bit ambiguous to me. Does it support async with a dependency on tokio if it is enabled, or is the crate only designed to support async?

If the latter, do you have any plans on supporting non-async?

@mdecimus
Copy link
Member

mdecimus commented Jun 2, 2022

Hi,
At the moment the library only supports async using Tokio, there is no support for other runtimes or blocking. However, non-async should be fairly easy to implement (just two functions need to be changed) so as soon as I have some time I'll do it.

@mripard
Copy link
Author

mripard commented Jun 3, 2022

awesome, thanks :)

@spikecodes
Copy link

maybe-async-rs is a fantastic crate that could definitely help with this. It is a selection of procedural macros that easily allow crate developers to make their code both compatible for async (it supports using tokio and async-std as the backends) and sync through the use of a crate feature.

@mdecimus
Copy link
Member

mdecimus commented Jun 4, 2022

@spikecodes Thanks, I'll have a look at it next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants