Skip to content

internal: allow clippy::large_unopt_stack_frames - #186

Merged
nbdd0121 merged 1 commit into
mainfrom
dev/clippy
Nov 17, 2026
Merged

nbdd0121 merged 1 commit into
mainfrom
dev/clippy

Conversation

@nbdd0121

Copy link
Copy Markdown
Member

Since Rust 1.102, Clippy renames large_stack_frames to large_unopt_stack_frames and make it warn by default. This is a good thing as in such cases pin-init should be used rather than potentially leave unoptimized large moves on stack. However, this also triggers in unexecutable code paths that pin-init generates for field duplication and exhaustiveness checks. Allow it on the generated check closure.

Since Rust 1.102, Clippy renames `large_stack_frames` to
`large_unopt_stack_frames` and make it warn by default. This is a good
thing as in such cases pin-init should be used rather than potentially
leave unoptimized large moves on stack. However, this also triggers in
unexecutable code paths that pin-init generates for field duplication and
exhaustiveness checks. Allow it on the generated check closure.

Signed-off-by: Gary Guo <gary@garyguo.net>
@nbdd0121
nbdd0121 merged commit 578ad6b into main Nov 17, 2026
59 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant