Stabilize bindings_after_at

[MarcusDunn]

attempting to stabilze bindings_after_at #65490, im pretty new to the whole thing so any pointers are greatly appreciated.

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @GuillaumeGomez (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[MarcusDunn]

Alright, I think this is mostly okay, I'm uncertain on what I should do with E0303.md as it references the removed feature flag, it also is no longer used so I do not know procedure for updating it. I've left it untouched for now but I think it should probably be changed in some way even if it's just there for historical reasons at the moment. I also am unsure if making this stable means anything for the reference. To me the feature seems more or less implied by the reference currently, but I think an example of it would not go ammiss in the patterns section. I'm also aware that somewhere in here there's a stabilization report needed, I have no idea what that would look like as the examples I can find all have accosiated RFC's whereas bindings_after_at was removed prior to 1.0 and is now being added back in (afaik).

[GuillaumeGomez]

r? @pnkfelix

[workingjubilee]

Fetched in submodule path 'src/doc/reference', but it did not contain f2803ae48185e5c3d900ebd27b79976724570967. Direct fetching of that commit failed.

@MarcusDunn The reference is a submodule, it cannot actually be directly affected from here. You should git reset HEAD~1 --hard, force push that (this will remove the reference commit that is convincing CI the world is broken), and open another PR against rust-lang/reference in order to apply changes against it.

[bors]

☔ The latest upstream changes (presumably #85458) made this pull request unmergeable. Please resolve the merge conflicts.

[bors]

☔ The latest upstream changes (presumably #85078) made this pull request unmergeable. Please resolve the merge conflicts.

[bors]

☔ The latest upstream changes (presumably #85734) made this pull request unmergeable. Please resolve the merge conflicts.

[workingjubilee]

Because this is a language feature, /compiler/* and /library/* will require allowing the feature during bootstrap only, so that the bootstrap compiler opens the feature gates still while the next compiler stage does not.

#![cfg_attr(bootstrap, feature(bindings_after_at))]

[workingjubilee]

Stabilization report is here.
Nominating for T-lang.

[rfcbot]

The final comment period, with a disposition to merge, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

The RFC will be merged soon.

[programmerjake]

ping, shouldn't this be merged now?

[pnkfelix]

@bors r+

[bors]

📌 Commit c2af4cb has been approved by pnkfelix

[bors]

⌛ Testing commit c2af4cb with merge 998cfe5...

[bors]

☀️ Test successful - checks-actions
Approved by: pnkfelix
Pushing 998cfe5 to master...