Jake Goulding

> in other words, converting `Result` to `Option` and using SNAFU's `OptionExt` instead of `ResultExt`. `.ok()` is nice and short, Notably, it's shorter than my proposed function: ```rust "42".parse::().ok().context(Parsing); "42".parse::().lossy_context(Parsing);...

Some people may also be interested in #78.

One thing mentioned in #192 is this: ```rust ContextSelector {/* ... */}.fail(); ``` Applied, it would look like ```rust use snafu::{Backtrace, Snafu}; #[derive(Debug, Snafu)] enum Error { InvalidType { v:...

Comparing the two possibilities shows it's only a single character difference: ```rust InvalidType { v }.fail()? bail!(InvalidType { v }) ```

The [documentation for enzyme covers this case](https://github.com/airbnb/enzyme/blob/master/docs/guides/jsdom.md#using-enzyme-with-jsdom).

> very inefficient code with 8x single bit shift That's a side-effect of some 16-bit fakery that happens. Multiplication should be able to be gated; there's a `supportsMultiplication` flag scattered...

> damn this problem sucks Is there _any_ hope for splitting up the concept of "pointer size" and "legal size"?

This content can start with the stuff [from the old wiki](https://github.com/avr-rust/rust-legacy-fork/wiki)

I can't directly answer your question, but I can point at two real-world examples: - https://github.com/avr-rust/blink/blob/master/avr-atmega328p.json - https://github.com/shepmaster/rust-arduino-blink-led-no-core-with-cargo/blob/master/avr-atmega328p-new.json

> This change makes it possible to finish the last exercise without touching the test code I'm surprised at this PR as **now** I can't implement the function _without_ changing...