-
Notifications
You must be signed in to change notification settings - Fork 2
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
cargo update
& lint/clippy/rustfmt/cargo-deny fixes.
#3
Conversation
Oops, just noticed "Ensure compatibility with rust-gpu nightly rust version" check doesn't actually do anything because of how the |
bdf3dcf
to
e018d86
Compare
"Ensure compatibility with rust-gpu nightly rust version" check works now, it even fully builds with only this warning:
(if we were running |
cargo update
& lint/clippy/rustfmt fixes.cargo update
& lint/clippy/rustfmt/cargo-deny fixes.
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 won't pass CI until #3 lands)* Similar to EmbarkStudios/spirt#61, the main reason for the bump is to avoid being stuck behind on definitions in a new release (even when there's not much going on).
This fixes the remaining CI failures.
The
rustfmt.toml
change was prompted by @Firestar99's formatting changes in #2, and the subsequent local rebasing, withversion = "Two"
causing warnings due to:So the perma-unstable
rustfmt.toml
version
config is nowstyle_edition = "2024"
, and hopefully that gets stabilized at the same time as Rust 2024 becoming stable.