Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking issue for release notes of #74939: Tracking issue for const <*const T>::is_null #133113

Closed
3 tasks
rustbot opened this issue Nov 16, 2024 · 2 comments
Closed
3 tasks
Labels
A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Milestone

Comments

@rustbot
Copy link
Collaborator

rustbot commented Nov 16, 2024

This issue tracks the release notes text for #74939.

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).

# Stabilized APIs
These APIs are now stable in const contexts:
- `<ptr>::is_null`
- `<ptr>::as_ref`
- `<ptr>::as_mut`

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 @oli-obk -- origin issue/PR authors and assignees for starting to draft text

@rustbot rustbot added A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-const-fn relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Nov 16, 2024
@jieyouxu
Copy link
Member

Stabilization PR: #133116

@RalfJung RalfJung added this to the 1.84.0 milestone Dec 5, 2024
@RalfJung
Copy link
Member

RalfJung commented Dec 5, 2024

I manually set the milestone since that's the release that will contain this stabilization. I hope that was the right thing to do, but I am not sure what the workflows are for this new relnotes automation.

@BoxyUwU BoxyUwU closed this as completed Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants