Closed
Description
Update(2018-08-28)
This is a tracking issue for the RFC "stable mechanism to specify the behavior of panic! in no-std applications " (rust-lang/rfcs#2070).
Steps:
- Implement the RFC
- Adjust documentation (see instructions on forge)
- The doc-comment of libcore mentions
rust_begin_panic
- The doc-comment of libcore mentions
- Stabilization PR (see instructions on forge)
Unresolved questions:
fmt::Display
Should the Display
of PanicInfo
format the panic information as "panicked at 'reason', src/main.rs:27:4"
, as "'reason', src/main.rs:27:4"
, or simply as
"reason"
.
Unwinding in no-std
Is this design compatible, or can it be extended to work, with unwinding
implementations for no-std environments?
Issues to solve before stabilization
- panic_implementation: Error message still talks about the panic_fmt lang item when missing panic_implementation: Error message talks about the panic_impl lang item when missing #51341
- panic_implementation: no_mangle attribute needed? panic_implementation: no_mangle attribute needed? #51342
-
rust_begin_unwind
not emitted when crate-type = binrust_begin_unwind
not emitted when crate-type = bin #51671
Metadata
Metadata
Assignees
Labels
Blocker: Approved by a merged RFC but not yet implemented.Category: An issue tracking the progress of sth. like the implementation of an RFCCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.Working group: Embedded systemsThis issue / PR is in PFCP or FCP with a disposition to merge it.The final comment period is finished for this PR / Issue.