Jake Goulding
Jake Goulding
> Ah, seems like the section titles are generally all-caps If it makes you feel any better, I do spell it the right way in the pre-stylized code 😉 :...
[Tests passed](https://github.com/rust-lang/rust-playground/actions/runs/13657556260?pr=1074)
Thank you for your patience.
Ah, I see #83 touches some (or all) of this.
This is not possible today, but I can see a path to supporting this on unstable Rust. Right now, `Report` does [not show backtraces in stable Rust](https://docs.rs/snafu/latest/snafu/struct.Report.html#interaction-with-the-provider-api). It requires access...
> is there a shorter, nicer way? I can't think of any technical reason that `snafu::Whatever` could not add an implementation of `From` (or `&str` or `AsRef`, etc. whatever works...
Sorry for the long delay! My initial reaction with minimal time spent thinking is ["no, we probably won't do that"](https://github.com/integer32llc/margo/blob/main/CONTRIBUTING.md). Notably, I chose to use [Tailwind](https://tailwindcss.com) for Margo, which means...
> adding a method to `Utf8Error` that returns the valid prefix Is that backwards-compatible? To do this, `Utf8Error` would need to gain a lifetime parameter and the signature of `from_utf8`...
> I need to implement `impl From for where T: Into` (I'm interpreting this as `impl From for OpaqueError where T: Into`) I was originally planning on writing a paragraph...
> and it seems to only support newtypes. Yes, this issue is indeed focused on opaque error types, as suggested by the issue title and the branch name. I'd encourage...