ICE on Rust 1.69.0 #495

Closed
opened 2026-09-09 19:05:03 -05:00 by KodrAus · 1 comment
KodrAus commented 2026-09-09 19:05:03 -05:00 (Migrated from github.com)

We previously worked around a rustdoc bug: https://github.com/bitflags/bitflags/issues/320

But I removed that workaround while doing some other work on the macro internals. It seems like that's triggering an ICE on 1.69.0 for downstream crates: https://github.com/nix-rust/nix/pull/2812

Since our MSRV is advertised as 1.56.0, we should try to re-fix this issue.

cc @xtqqczze

We previously worked around a `rustdoc` bug: https://github.com/bitflags/bitflags/issues/320 But I removed that workaround while doing some other work on the macro internals. It seems like that's triggering an ICE on `1.69.0` for downstream crates: https://github.com/nix-rust/nix/pull/2812 Since our MSRV is advertised as 1.56.0, we should try to re-fix this issue. cc @xtqqczze
KodrAus commented 2026-09-09 19:07:07 -05:00 (Migrated from github.com)

Having a look at the diff, I think I may have done this just to avoid duplicating the set of allowed attributes. Hopefully that's the case and there's not some other issue uncovered by moving that impl back outside of the const block.

Having a look at the diff, I think I may have done this just to avoid duplicating the set of allowed attributes. Hopefully that's the case and there's not some other issue uncovered by moving that `impl` back outside of the `const` block.
Sign in to join this conversation.
No labels
bug
good first issue
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-bitflags/bitflags#495
No description provided.