maybe-async-rs

maybe-async-rs copied to clipboard

async and sync in the same program

23

I maintain some libraries that have sync and async users. The async users wrap calls in `spawn_blocking`, which works, but isn't ergonomic and may be suboptimal. `maybe_async` looks like it...

sunfishcode

`maybe_async::test` does not seem to work in a `test` module

1

I have the following test case: ``` #[cfg(test)] mod tests { #[cfg(feature = "async")] use tokio; #[maybe_async::test( feature="blocking", async(feature = "async", tokio::test) )] async fn test_oauth() { ... let client...

juliankrieger

qiuchengxuan

dtolnay

Async traits implementation from nightly

2

This crate currently uses the `async_trait` crate to support async functions in traits. My understanding of async is not very deep but I wonder if it would be possible to...

Niederb

Add `legacy-syntax` and `syn-2` features

6

This PR does essentially two things: - Adds an enabled-by-default feature `legacy-syntax` and gates the `test` macro behind that feature - Adds a `syn-2` feature to enabled use of `syn`...

smoelius

maybe-async breaks crates

1

Hey! I just noticed something that seems kind of bad! The `is_sync` feature of maybe-async breaks stuff. Here's an example: Create a new, empty crate, add these dependencies: ```toml crates-index...

xfbs

`maybe_async` on structs

1

According to the readme I can apply the macro to struct definitions. However if I do this on an `impl` block for a struct (without trait) I get an error...

Niederb

Updates the requirements on [syn](https://github.com/dtolnay/syn) to permit the latest version. Release notes Sourced from syn's releases. 2.0.4 Improve error reporting when parsing identifiers and paths (#1415, #1416) Commits 91ca7c0 Release...

dependabot[bot]

When using `#[maybe_async::maybe_async(AFIT)]` on public traits, I get the following warning: `use of "async fn" in public traits is discouraged as auto trait bounds cannot be specified`. I understand why...

yanshay