-
Notifications
You must be signed in to change notification settings - Fork 999
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
Error Shown in VSCode : add reference here rust-analyzer #2348
Comments
I may have found a fix for the error, @canewsin could you test if you still get it on https://github.com/elenaf9/rust-libp2p/tree/swarm-derive/inject-dial-error? |
Issue Fixed. |
`NetworkBehaviour::inject_dial_failure` expects a reference for the error, thus the error should not be cloned when passing it to the inner behaviours in the `NetworkBehaviour` derivation. Fixes Issue #2348.
Closing here since #2349 is merged. |
@mxinden Since this is a show-stopper for releasing against libp2p 0.41, would it be possible to release libp2p-swarm-derive 0.26.1 soon? |
I can cut |
Hmm, you’re right — I didn’t actually try building with rustc when I saw the kind of error (which usually means that without a In any case, I depend on rust-analyzer, and I learnt to only trust its output when there are no errors in the project at all, which means I’d still prefer this to be released sooner rather than later :-) |
Perhaps 0.26.1 of this crate is enough for starters, libp2p 0.41.2 could have more things. |
I plan to release |
sure! |
When deriving NetworkBehaviour.
This doesn't stop the code compilations.
Even code examples have these errors.
The text was updated successfully, but these errors were encountered: