review color_die and color_warn usage, deciding when it's appropriate to print the stack
As suggested by @goneri but without the Carp::Always dependency or global override.
Using
perl -MCarp::Always cf-sketch.pl ...options...
is a very nice way to get stack traces during development, so at least in that context it's a very useful module.
During my rewrite I replaced a lot of calls to color_warn/die to Util::error and Util::warning, with the intention of printing user-friendlier messages without stack traces and such. It should indeed be reviewed to decide when we need to print a user-readable message vs a developer-friendly message.
Maybe color_die/color_warn should check if Carp::Always is loaded and defer to warn/die if so?
Then we can add --carp to the option list so you don't have to use -MCarp::Always