Freja Roberts
Freja Roberts
> the main rough edge to watch out for is accidentally using `Into` instead of `IntoReport` and losing context. > > you might be able to catch these at runtime...
Some further consideration and ideas regarding this: 1. We allow `std::error::Error` and `IntoEyre` to coexist, and while the user can use `?` and lose some context, they can go back...
Thank you for bringing this to attention. We debated last week about trying autocfg, as I've used it before with success. I'll see if I can push out a branch...
Regarding the open issues you mentioned on autocfg, as well as https://github.com/cuviper/autocfg/pull/43 we are not able to detect using just autocfg if we have backtraces or nightly available. My idea...
Related: #147 and https://github.com/eyre-rs/eyre/pull/138#discussion_r1432909562
Furthermore, it would provide a common CI between the crates, which ensures that each of the subcrates, such as `color-eyre` also gets tested and a single PR can test regressions...
Hey there, this looks related to #84 , which is to be fixed by #160. Would you mind giving the branch a spin?
:sweat_smile: Just saw your PR @thenorili, I accidentally fixed it too while working on another compile probe issue in #160. Any chance we could merge that first and then look...
@thenorili I've fixed up the commit message now and cleanup up the PR, let me know what you think :blush: