-
Notifications
You must be signed in to change notification settings - Fork 660
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
toolchain: update to Rust 1.68.0 #8721
Conversation
Routine update to the latest version of Rust. Release post: https://blog.rust-lang.org/2023/03/09/Rust-1.68.0.html I don't see anything exciting for nearcore in the release. Maybe `pin!` for custom futures could be useful. The commit also includes clippy renaming `derive_hash_xor_eq` to `derived_hash_with_manual_eq`. There is also a new [future incompatibility warning](rust-lang/rust#103418) which we hit in `fs_extra v1.2.0` and `wasmparser v0.78.2`. I don't think we can get rid of the second anytime soon, assuming we hang on to replayability.
core/crypto/src/signature.rs
Outdated
@@ -160,7 +160,7 @@ impl PublicKey { | |||
|
|||
// This `Hash` implementation is safe since it retains the property | |||
// `k1 == k2 ⇒ hash(k1) == hash(k2)`. | |||
#[allow(clippy::derive_hash_xor_eq)] | |||
#[allow(clippy::derived_hash_with_manual_eq)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This, I believe, should no longer be necessary, as the rename is a part of the changes that now allow manual implementation of hash regardless of how the Eq
implementation is produced.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh, yes makes sense. Removed them.
these are no longer needed
Routine update to the latest version of Rust.
Release post: https://blog.rust-lang.org/2023/03/09/Rust-1.68.0.html
I don't see anything exciting for nearcore in the release.
Maybe
pin!
for custom futures could be useful.The commit also includes clippy changes, they renamed
derive_hash_xor_eq
toderived_hash_with_manual_eq
and changed the check. Now, we no longer need an
allow()
.There is also a new future incompatibility warning
which we hit in
fs_extra v1.2.0
andwasmparser v0.78.2
.I don't think we can get rid of the second anytime soon, assuming we
hang on to replayability.