-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Update code to remove lots of warnings from Rust 1.83 #15593
base: main
Are you sure you want to change the base?
Conversation
⏱️ 5h 31m total CI duration on this PR
🚨 3 jobs on the last run were significantly faster/slower than expected
|
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.
I reviewed the stuff I'm familiar with (faucet, CLI, indexer) pretty closely and skimmed the rest, looks good.
@@ -305,6 +305,7 @@ impl CheckerTrait for RedisRatelimitChecker { | |||
|
|||
/// All we have to do here is decrement the counter if the request was a failure due | |||
/// to something wrong on our end. | |||
#[allow(dependency_on_unit_never_type_fallback)] |
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.
Allowing this seems fine to me for now, the proper never type (!
) isn't even stable yet, we'll revisit it later when it is.
} else { | ||
num_tasks | ||
} | ||
num_tasks.clamp(1, MAX_FETCH_TASKS_PER_REQUEST) |
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.
Neat
This comment has been minimized.
This comment has been minimized.
5df4772
to
ed657e0
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
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.
VM side is ok, interesting that same attributes with different arguments are considered the same by linter now.
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.
I've reviewed the move compilers, linter etc under third-party.
@@ -11,7 +11,7 @@ use move_core_types::metadata::Metadata; | |||
use move_ethereum_abi::abi_move_type::{ABIMoveSignature, ABI_ETHER_MOVE_KEY}; | |||
use std::{collections::BTreeMap, str}; | |||
|
|||
/// Generate Metadata for move signature | |||
// Generate Metadata for move signature |
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.
Perhaps we should keep the ///
comment, but remove the empty lin below?
Description
There are a ton of warnings for mostly cosmetic things added to Rust 1.83. For anything that was complex, or required renaming, I added an
allow
.Otherwise main things changed:
'_
or sometimes named specifically'a
, each are approached correctly.ceil_div
implementations and adds them accordinglydead_code
annotation is addedHow Has This Been Tested?
We're running the full testsuite on this PR to ensure it works.
Key Areas to Review
For each area, please review and ensure there is no behavior change. For the Move compiler, and storage, most of the changes are just removing
<'a>
and moving to'_
as per the compiler.Type of Change
Which Components or Systems Does This Change Impact?
Checklist