Jake Goulding
Jake Goulding
While taking to @dtolnay about #928, we realized that **release** mode procedural macros are rebuilding dependencies (and may always have been). They had this as a suggestion: > The goal...
Spawned from #184. We could link to the docs, repo, crates.io pages, show the versions, a one-line description? 
# Before merging - [ ] Discuss "tied" / "untied" terminology - [ ] Discuss "deprecated" terminology - [ ] Discuss the `async fn` hard error case. --- Types that...
Originally added in #395, we [discovered](https://github.com/shepmaster/snafu/pull/428#pullrequestreview-1795424280) it caused some type inference issues. In order to release 0.8 with new features, I'm reverting that code for now.
In #398, we discussed the possibility of changing `IntoError` to look something like ```rust trait IntoError { fn into_error(source: S, context: C) -> Self; } ``` I think this would...
We assume that there will be `String`, among other things: ``` error[E0432]: unresolved import `crate::FromString` --> /Users/shep/.cargo/registry/src/index.crates.io-6f17d22bba15001f/snafu-0.7.4/src/futures/try_stream.rs:5:33 | 5 | use crate::{Error, ErrorCompat, FromString, IntoError}; | ^^^^^^^^^^ no `FromString` in...
```rust r.unwrap_report(); ``` This would basically boil down to ```rust match r { Ok(v) => v, Err(e) => panic!("{}", snafu::Report::from_error(e)), } ```
Right now we do ```rust SomeContextSelector { foo, bar }.fail()? ``` With the `Try` trait, we should be able to shorten that to ```rust SomeContextSelector { foo, bar }? ```
These changes have been running in production for a while after I hand-applied them. The Ansible-specific changes are mostly to see that the managed changes match close enough to the...