-
Notifications
You must be signed in to change notification settings - Fork 64
rustup: update to nightly-2025-06-23
(~1.89).
#320
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
78093b6
to
9b17fca
Compare
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 don't see anything obvious but admittedly am not qualified to review this.
let align_override = | ||
Some(alloc.align).filter(|&align| align != self.lookup_type(value_ty).alignof(self)); | ||
if let Some(_align) = align_override { | ||
// FIXME(eddyb) implement, or at least error. |
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.
todo!()
these? I don't know this code so don't know if needed.
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.
todo!()
would ICE, it should at the very least be a nice user error if we do want to enforce it.
(otherwise, e.g. assert_eq!(alloc.align, self.lookup_type(value_ty).alignof(self))
is much better than a todo!()
, but I don't think we should do either)
These things used to be ignored before, too, I just made the code slightly clearer that that's happening.
Not much to see this time, other than:
format_args!
complications (less efficient codegen for some reason)-Zshare-generics=off
now being needed (because of weird special-casing done tocompiler-builtins
otherwise leaking to shader crates, via e.g.<Range<usize> as Iterator>>:next
)clippy::collapsible_if
, it's surprisingly applicable)