Skip to content

Tracking issue for release notes of #159504: Abort const-eval queries early when there are generics in the type #160263

Closed
Closed
Tracking issue for release notes of #159504: Abort const-eval queries early when there are generics in the type#160263
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.99.0

Description

@rustbot
rustbot
opened on Jul 31, 2026

This issue tracks the release notes text for #159504.

cc @RalfJung, @BoxyUwU -- 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
- [Abort const-eval when there are generics in the type of the value being produced](https://github.com/rust-lang/rust/pull/159504)

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 this to the  1.99.0 milestone on Jul 31, 2026
  2. 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 Jul 31, 2026
  3. RalfJung commented on Jul 31, 2026 
    @RalfJung
    RalfJung
    on Jul 31, 2026
    Member
    @lcnr why did you label this with relnotes?
  4. lcnr commented on Jul 31, 2026 
    @lcnr
    lcnr
    on Jul 31, 2026
    Contributor
    Is this in any way observable? wasn't sure whether it would be and when going through the list of all merged PRs I would rather err on the side of marking things incorrectly
  5. lcnr commented on Jul 31, 2026 
    @lcnr
    lcnr
    on Jul 31, 2026
    Contributor
    I think it doesn't? In which case, feel free to close this again
  6. RalfJung commented on Jul 31, 2026 
    @RalfJung
    RalfJung
    on Jul 31, 2026
    Member
    I don't think #159504 changed anything... #156977 fixed the underlying ICE and may have also broken some really obscure code out there but I am not sure yet (the crater run is still in the queue).
  7. jieyouxu
    removed 
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
     on Aug 28, 2026
  8. BoxyUwU commented on Sep 4, 2026 
    @BoxyUwU
    BoxyUwU
    on Sep 4, 2026
    Member
    I'll keep it in compat notes just in case 🤷‍♀️
  9. cuviper
    closed this as completedon Oct 10, 2026
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