Currently backtrace is a hard dependency (and a heavy one at that), and there is no middle-ground between simple-eyre and color-eyre.
I believe most people want/need the colours/formatting and extra sections & suggestion helpers, however backtraces are very seldom used, end-users don't care about them, and they're not even available in properly-built release binaries anyway.
I would like to propose moving it behind a feature flag at least, allowing people to use the extras that color-eyre provides, without the unnecessary cruft inflating build times & binaries.
To clarify: i'm talking about all backtrace functionality, including the dependency.
Currently the only workaround is to use anyhow in no_std mode, so not even the environment variables have an effect.
Edit: it seems even if the dependency was optional, backtraces are still forced via the build-script + cfg attribute, why is everyone so obsessed with them.
Currently
backtraceis a hard dependency (and a heavy one at that), and there is no middle-ground betweensimple-eyreandcolor-eyre.I believe most people want/need the colours/formatting and extra sections & suggestion helpers, however backtraces are very seldom used, end-users don't care about them, and they're not even available in properly-built release binaries anyway.
I would like to propose moving it behind a feature flag at least, allowing people to use the extras that
color-eyreprovides, without the unnecessary cruft inflating build times & binaries.To clarify: i'm talking about all backtrace functionality, including the dependency.
Currently the only workaround is to use
anyhowinno_stdmode, so not even the environment variables have an effect.Edit: it seems even if the dependency was optional, backtraces are still forced via the build-script + cfg attribute, why is everyone so obsessed with them.