Track upstream double-panic issue

Open
#620 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
documentation, embedded-iot

Research direction

Start with upstream Rust issue 97146, then inspect the re-book and re-nomicon documentation references mentioned here. Check whether panic-persist, panic-probe, and other non-trivial panic handlers need follow-up issues. Done means the affected documentation and related projects are identified and tracked.

Written by the indexing model from the issue text.

Description

We should probably track the upstream https://github.com/rust-lang/rust/issues/97146, to make sure to update docs to explicitly mention this.

It probably just means updating the re-book and re-nomicon, but might have other ripples, and we should probably open issues in projects like panic-persist, panic-probe, and any other panic handlers that do something non-trivial.

Dominant language
No language data
Stars
2.1k
Forks
116
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-embedded/wg

All issues in rust-embedded/wg

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.