-
Notifications
You must be signed in to change notification settings - Fork 5k
chore: upgrade to Rust 1.89 #2465
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
Conversation
5ac2cbe
to
c6f4144
Compare
3cc22c0
to
76d33fc
Compare
out.extend_from_slice(&commands[idx + 1..]); | ||
return Some(out); | ||
} | ||
}) && commands |
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'm in favor of standardization but some of these feel a bit complicated
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.
Understood, though it is a losing battle against Clippy (unless we choose to disable this rule?). I think, in general, avoiding the nested if
s is for the best.
@@ -309,7 +309,7 @@ where | |||
} | |||
|
|||
/// Get a Frame object which provides a consistent view into the terminal state for rendering. | |||
pub fn get_frame(&mut self) -> Frame { | |||
pub fn get_frame(&mut self) -> Frame<'_> { |
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.
unrelated lifetime change? Or is this newly required to be explicit?
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.
Good eye!
Yes, it appears this has changed:
https://blog.rust-lang.org/2025/08/07/Rust-1.89.0/#mismatched-lifetime-syntaxes-lint
) The `ubuntu-24.04 - x86_64-unknown-linux-gnu` build is failing with `No space left on device` on #2465, so let's get this in first, which should help. Note that `cargo check` should be faster and use less disk than `cargo build` because it does not write out the object files.
Codex created this PR from the following prompt:
Note this modifies a lot of lines because it folds nested
if
statements using&&
.Stack created with Sapling. Best reviewed with ReviewStack.