Construct Error with existing backtrace
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start by locating Error::new and the existing Backtrace handling in the anyhow source. Review how errors are currently constructed under stable Rust, then determine the public API shape for passing a previously captured Backtrace. Done means the requested construction path exists and is covered by tests for preserving the supplied backtrace.
Written by the indexing model from the issue text.
Description
Currently the only way to construct an anyhow::Error with a backtrace that we previously captured is through the (still) unstable error_generic_member_access feature. Would like to have a variant of the Error::new function that allows you to pass a Backtrace as well.
- Dominant language
- Rust
- Stars
- 6.7k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from dtolnay/anyhow
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
`ensure!` doesn't accept inline const blocksPossibly taken @FadeHack claimed this 85 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 74/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
Similar issues
-
Selected chart highlights only its values, not its series names and category labelsPossibly taken @Higgs32584 claimed this today. Openbug priority: low ui
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/gridcraft#4390 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug bugfix priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
quarto-dev/q2#1219 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
BurntSushi/jiff#713 ·
Maintainers usually reply within 1 day