Discussion: Allowing `.suggestion()` and other sections on `eyre!()` macro. about color-eyre

[Mythra]

Sounds great @yaahc , thanks for the quick, and helpful response ❤️ !

[yaahc]

This is caused by the separation between eyre and color-eyre and the way its currently designed. The eyre! macro is exported by the eyre crate, which knows nothing about color-eyre or its notion of sections. The type that is returned from eyre! is a Report<H> where H hasn't been resolved. And then, to make this all worse the note function and other section modifying functions are similarly defined outside of eyre via an extension trait. It might be possible for me to add an identical trait to SectionExt that works directly on Report rather than being a combinator that applies to Reports inside of Results, so it might be possible to fix this but ultimately it doesn't matter.

All of this boils down to the fact that eyre's 0.4 release depends on generics to specify the handler type. The next release of eyre, which I'm aiming to get out today, removes the generic parameter and instead uses a globally installed hook to construct handler trait objects which can be boxed and stored by eyre!. On the next release this should "just work".

[yaahc]

My pleasure, ty for the helpful suggestions!

side note, if you're interested in trialing the new release and helping me catch any issues I may have missed pre release now is the time. The only thing left to do is to update the documentation to reflect the new reality of how everything works and possibly tweek a few of the interfaces to be easier to use.

Here's the relevant include if you're interested

color-eyre = { git = "https://github.com/yaahc/color-eyre.git", branch = "hooked" }