chore: bump the nightly pin 2026-04-26 → 2026-07-30 (+ fork §11) - #25
Merged
Conversation
The 3-month-old pin was due; done deliberately + fully re-verified per the rust-toolchain.toml policy, well before the Evoke deadline. Two things the newer nightly forced, both small: - rust-lang/rust#158758 RENAMED the `lazy_type_alias` feature gate to `checked_type_aliases`, so bevy_gaussian_splatting's `nightly_generic_alias` feature failed E0557 on any post-rename nightly. Fixed in the fork (martin-tightcut §11, one word in lib.rs); the git rev pin moves 608c7d1 → f94855a. Upstream will need the same fix. - New clippy lint `chunks_exact_to_as_chunks`: 4 sites (stereo→mono averaging in audio/analyze.rs, triangle-index walks in mesh.rs + scene/gl_dissolve.rs) now use `as_chunks::<N>()` — same shape, and the compiler gets constant-size chunks. Docs: DESIGN.md / Cargo.toml fork comments §1–10 → §1–11, OPTIMIZATION-BACKLOG.md pinned-rev note. Verified on nightly-2026-07-30: build --release (sh0 AND sh3), fmt --check, clippy -D warnings, 176 tests, reuse lint, `martin --validate`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 3-month-old pin was due; done deliberately + fully re-verified per the
rust-toolchain.tomlpolicy, well before the Evoke deadline.Two things the newer nightly forced, both small:
lazy_type_aliasfeature gate tochecked_type_aliasesrust-lang/rust#158758 renamed thelazy_type_aliasfeature gate tochecked_type_aliases— bevy_gaussian_splatting'snightly_generic_aliasfeature failed E0557 on any post-rename nightly. Fixed in the fork (martin-tightcut§11, one word inlib.rs); the git rev pin moves608c7d1→f94855a. Upstream (mosure) will need the same fix.chunks_exact_to_as_chunks— 4 sites (stereo→mono averaging inaudio/analyze.rs, triangle-index walks inmesh.rs+scene/gl_dissolve.rs) now useas_chunks::<N>(). Same shape; the compiler gets constant-size chunks.Docs: DESIGN.md / Cargo.toml fork comments §1–10 → §1–11, OPTIMIZATION-BACKLOG.md pinned-rev note.
Verified on nightly-2026-07-30
cargo build --release— sh0 AND sh3 ✅cargo fmt --all --check✅cargo clippy --all-targets -- -D warnings✅cargo test --release— 176 passed ✅reuse lint— compliant ✅martin --validateon the default show ✅Note:
cargo buildnow also surfaces future-incompat warnings from naga/wgpu 29, nix, winit — pre-existing upstream dep code, informational only, will resolve with the next Bevy bump.🤖 Generated with Claude Code