Tracking Issue for `breakpoint` feature (`core::arch::breakpoint`)
Open
Nobody has claimed this yet.
C-tracking-issue
disposition-merge
finished-final-comment-period
I-lang-radar
T-lang
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(breakpoint)]
This is a tracking issue for the breakpoint feature, which gates the core::arch::breakpoint function. This feature was approved in ACP 491.
Public API
// core::arch
/// Compiles to a target-specific software breakpoint instruction or equivalent.
///
/// (Long description elided.)
#[inline(always)]
pub fn breakpoint() {
unsafe {
core::intrinsics::breakpoint();
}
}
Steps / History
- ACP: https://github.com/rust-lang/libs-team/issues/491
- Implementation: https://github.com/rust-lang/rust/pull/133726
- Final comment period (FCP)^1
- Stabilization PR with lang FCP
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the core::arch::breakpoint API and the stabilization PR linked under Steps / History, then review ACP 491 and the feature lifecycle requirements. Done means resolving any remaining concerns and completing the stabilization PR with lang FCP; the issue reports no unresolved questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100