Chris Krycho

Once I saw that it's a Django package more generally, I came to the same conclusion. Feel free to close this; I'll reopen it on the relevant project.

Since we're using [thiserror](https://crates.io/crates/thiserror), it should be straightforward to get backtraces throughout the application, and this does *not* require using `RUST_BACKTRACE`. We can then use `thiserror`'s support for `std::backtrace::Backtrace` to...

This'll need a rebase/merge courtesy of merging #1299. I'll tackle it on Monday.

Okay, that works… but now we have test failures because something isn't *quite* right in [e34264e](https://github.com/emberjs/ember-test-helpers/pull/1298/commits/e34264e69cf18a1117e35c0be6fd75b6d3668ae4), I think. Will poke at it… *after* getting a whole bunch more deck-clearing done...

For what it's worth, I experimented a bit with changing the *rendering* pass as part of trying to see how far I could get on the "standard" footnotes style with...

In case folks here aren’t familiar with Rust’s approach, here’s an example illustrating @pitaj’s point that it’s much more general than the `Option`/`Result`/`Try`/`?` behavior: ```rust enum ArbitraryData { Cool(String), Neat(i32),...

@stefanpenner thoughts on merging this and *then* fixing the `yarn run docs` side of things?

See emberjs/rfcs#785, which includes letting `render` take a component in support of getting rid of the need for `this.get` and (especially) `this.set` in rendering tests. 😄

This is most likely an issue with our upstream dependency on Clap, and will hopefully be resolved after we get to the latest version there (#1598).

It would be relatively straightforward to use [directories](https://crates.io/crates/directories) (referenced on the RFC mentioned immediately above) in place of the `~/.volta` directory, and I would personally be in support of that—it...