Skip to content

Conversation

@github-actions
Copy link
Contributor

🤖 New release

  • rustc-demangle: 0.1.26 -> 0.1.27 (✓ API compatible changes)
Changelog

0.1.27 - 2026-01-15

Other

  • Support v0 demangling of trait object types with assoc const bindings


This PR was generated with release-plz.

@BoxyUwU BoxyUwU closed this Jan 15, 2026
@BoxyUwU BoxyUwU reopened this Jan 15, 2026
@fmease fmease enabled auto-merge January 15, 2026 15:19
@fmease fmease merged commit ca5202e into main Jan 15, 2026
6 checks passed
@fmease fmease deleted the release-plz-2026-01-15T15-09-27Z branch January 15, 2026 15:19
rust-bors bot pushed a commit to rust-lang/rust that referenced this pull request Jan 20, 2026
mGCA: Make trait object types with type-level associated consts dyn compatible if all of the latter are specified via bindings

Under feature `min_generic_const_args` (mGCA) (#132980), render traits with non-parametrized type-level associated constants (i.e., `#[type_const]` ones) dyn compatible but force the user to specify all type-level associated consts in the trait object type via bindings (either directly, via supertrait bounds and/or behind trait aliases) just like associated types, their sibling.

Fixes #130300 (feature request).
Fixes #136063 (bug).
Fixes #137260 (bug).
Fixes #137514 (bug).

While I'm accounting for most illegal `Self` references via const projections & params, I'm intentionally ignoring RUST-123140 (and duplicates) in this PR which is to be tackled some other time.

Additional context: Crate `rustc-demangle` had to be updated to fix v0 demangling. I've patched it in PR rust-lang/rustc-demangle#87 which was was released in version 0.1.27 via PR rust-lang/rustc-demangle#88.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants