Skip to content

Tracking issue for release notes of #154992: Error on projection of dyn noncompat type in old trait solver #161194

Open
Open
Tracking issue for release notes of #154992: Error on projection of dyn noncompat type in old trait solver#161194
Labels
T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.relnotesMarks issues that should be documented in the release notes of the next release.relnotes-tracking-issueMarks issues tracking what text to put in release notes.
Milestone
1.100.0

Description

@rustbot
rustbot
opened on Aug 16, 2026

This issue tracks the release notes text for #154992.

cc @spirali, @lcnr -- original issue/PR authors and assignees for drafting text

See the forge.rust-lang.org chapter about release notes for an overview of how the release team makes use of these tracking issues.

Release notes text

This section should be edited to specify the correct category(s) for the change, with succinct description(s) of what changed. Some things worth considering:

  • Does this need an additional compat notes section?
  • Was this a libs stabilization that should have additional headers to list new APIs under Stabilized APIs and Const Stabilized APIs?
# Compatibility Notes
- [Check dyn-compatibility of trait objects in more places](https://github.com/rust-lang/rust/pull/154992)

Tip

Use the previous releases for inspiration on how to write the release notes text and which categories to pick.

Release blog section

If this change is notable enough for inclusion in the blog post then this section should be edited to contain a draft for the blog post. Otherwise leave it empty.



Note


If a blog post section is required the release-blog-post label should be added (@rustbot label +release-blog-post) to this issue as otherwise it may be missed by the release team.


Activity
  1. rustbot
    added 
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
     
    relnotesMarks issues that should be documented in the release notes of the next release.
     
    relnotes-tracking-issueMarks issues tracking what text to put in release notes.
     
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
     on Aug 16, 2026
  2. Rails-Ruby commented on Aug 16, 2026 
    @Rails-Ruby
    Rails-Ruby
    on Aug 16, 2026 · Hidden as spam
  3. rustbot
    added this to the  1.100.0 milestone on Aug 22, 2026
  4. rust-lang
     blocked Rails-Rubyon Aug 26, 2026
  5. jieyouxu
    removed 
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
     on Aug 28, 2026
  6. theemathas commented on Oct 5, 2026 
    @theemathas
    theemathas
    on Oct 5, 2026
    Contributor
    @lcnr I saw that you wrote "Always require trait objects to be dyn-compatible", but this isn't accurate. The below code still compiles. What should the correct release notes be?
    

    trait Trait: Sized {}
type Lol = dyn Trait;
  7. lcnr commented on Oct 6, 2026 
    @lcnr
    lcnr
    on Oct 6, 2026
    Contributor
    "always require trait objects to be dyn-compatible modulo free type aliases and normalization being horrible" :> adjusted it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Metadata
Assignees
No one assigned
    Labels
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.relnotesMarks issues that should be documented in the release notes of the next release.relnotes-tracking-issueMarks issues tracking what text to put in release notes.
    Type
    No type
    Projects
    No projects
      Milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions