Skip to content

Tracking issue for release notes of #133392: Fix ICE when multiple supertrait substitutions need assoc but only one is provided #134308

New issue
New issue
Closed
Closed
Tracking issue for release notes of #133392: Fix ICE when multiple supertrait substitutions need assoc but only one is provided#134308
Labels
T-typesRelevant to the types 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.85.0

Description

@rustbot
rustbot
opened on Dec 14, 2024

This issue tracks the release notes text for #133392.

Steps

  • Proposed text is drafted by PR author (or team) making the noteworthy change.
  • Issue is nominated for release team review of clarity for wider audience.
  • Release team includes text in release notes/blog posts.

Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

# Compatibility Notes
- [Error if multiple super-trait instantiations of `dyn Trait` need associated types to be specified but only one is provided](https://github.com/rust-lang/rust/pull/133392)

Tip

Use the previous releases categories to help choose which one(s) to use.
The category will be de-duplicated with all the other ones by the release team.

More than one section can be included if needed.

Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
Otherwise leave it empty.



cc @compiler-errors, @lcnr -- origin issue/PR authors and assignees for starting to draft text
Activity
  1. rustbot
    added 
    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.
     
    T-typesRelevant to the types team, which will review and decide on the PR/issue.
     
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
     on Dec 14, 2024
  2. compiler-errors commented on Dec 14, 2024 
    @compiler-errors
    compiler-errors
    on Dec 14, 2024
    Contributor
    Probably doesn't need to be mentioned in the relnotes since it's pretty obviously only a theoretical regression..
  3. rustbot
    added this to the  1.85.0 milestone on Dec 15, 2024
  4. saethlin
    removed 
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
     on Dec 16, 2024
  5. lcnr commented on Dec 17, 2024 
    @lcnr
    lcnr
    on Dec 17, 2024
    Contributor
    I do think it should be mentioned. There is no harm in mentioning it and it's useful to point to this in the rare case that someone does encounter breakage because of this by accident
  6. compiler-errors commented on Dec 17, 2024 
    @compiler-errors
    compiler-errors
    on Dec 17, 2024
    Contributor
    Feel free to write something there then bc i won't lol
  7. lcnr commented on Dec 17, 2024 
    @lcnr
    lcnr
    on Dec 17, 2024
    Contributor
    already did so :3
  8. Mark-Simulacrum
    closed this as completedon Feb 15, 2025
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-typesRelevant to the types 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