-
`-> impl Send + Future` (since Rust 1.75) should be the preferred alternative.
-
Several crates in this repo could benefit from having `async` equivalents. There are several use cases for `async`, such as communicating with network services which implement a particular cryptograph…
-
Hello! I was wondering if there is interest in adding a trait for async drivers.
I am currently using an [Rmt async driver](
https://github.com/esp-rs/esp-hal/blob/main/esp-hal/src/rmt.rs#L287-L30…
-
I believe the async traits can be updated to use native syntax
There are caveats, but you can manually specify the `Send` bound on an explicit associated type.
See: https://blog.rust-lang.org/2023/1…
-
-
Thank you for the nice crate!
I needed support for specializing some method implementations in the generated traits for each case, while having a single implementation for the rest of the trait. Wh…
-
Make a version of the adapter trait async. This will allow remote adapter implementation (e.g redis adapter, mongodb adapter).
-
### Code
```rust
trait Trait {}
async fn fun() -> Trait {
todo!()
}
fn main() {}
```
### Current output
```
error[E0782]: expected a type, found a trait
--> src/main.rs:3:19
|
3 | async fn…
-
### What would you like to share?
#### Work Expected From The Issue
Redesign the `cache` internal api to move it away from using an OOP based design to a more composable enum based.
The issue exp…
-
These features are still unstable but not considered to be "incomplete" now! We can use them to simplify the async trait interfaces.
Already done:
- #8422
- #10120
- #10406
- https://github.co…