Closed appetrosyan closed 9 months ago
OK, so after some digging, I think I know what the problem is.
The offending module is doc.rs
where the implementation is made using the async_trait
but the trait defnition doesn't have it.
I'm unable to replicate the bug (Debian/amd64), what hardware are you finding this on?
Ryzen 2700x.
Just pulled and replaced the dependency with the specific path. And the problem went away.
This may be something with the cargo registry.
/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cqrs-es-0.4.10/src/doc.rs:42:5
OK so this is the offending file.
The latest commit in 0.4.10
is c2f7
, maybe that's the clue
Can't reproduce.
Rust now has native support for
async fn
in traits and implementations.For the time being, any attempt to compile with a cleaned up
Cargo.lock
results in the following:Minimum working example:
cargo new cqrs-es-test
cqrs-es-test
runcargo add cqrs-es
cargo check
.Proposed solution
Remove dependency on
async_trait
. It handles more edge cases than the currentrustc
solution, but those edge cases are likely to be resolved upstream.