-
Without this, it is impossible to conveniently use it with anyhow or thiserror.
-
Things we need to establish a convention for what we doing about `anyhow::Result` return types?
I've opened n0-computer/iroh#490 to explore idioms, and in this one I'm experimenting with defining a…
-
It is not possible to determine which tab is selected
-
I noticed a few things that could benefit this repo, but feel free to take it or leave it.
- Run `clippy` on your code. I did. There were numerous good suggestions that simplify the structure and l…
-
1.81 stabilizes the Error trait in core, allowing usage of the trait in #![no_std] libraries.
-
Error handling in `block2.rs` is currently downright disgusting. As discussed, we'll switch to pure-`anyhow` error handling for everything inside `block2.rs`. Recommended reading: the `anyhow` readme:…
-
Currently the tutorials start off using `anyhow` and switch to using `color_eyre`, something I did in all my projects while I was writing some of the tutorial material. If I were to write them from sc…
-
There are several places in the library that `panic!()` is called when an `Err(anyhow::anyhow!("Some description"))` would be more appropriate.
Using the `thiserror` crate would be even better, but…
-
With Rust 1.61.0 out, the [`Termination`](https://doc.rust-lang.org/stable/std/process/trait.Termination.html) trait and associated [`ExitCode`](https://doc.rust-lang.org/stable/std/process/struct.Exi…
-
```
use anyhow::Result;
use heapless::String;
pub fn test() -> Result {
let mut phrase = String::new();
phrase.push_str("XX")?;
Ok(phrase)
}
```
```
--> src/mnemonic.rs:31…