Systematize error-issuing and other printing functions #2129
Labels
tech debt
Issues that document or involve technical debt
topics: error-handling
Issues involving the way SAW responds to an error condition
topics: error-messages
Issues involving the messages SAW produces on error
Right now errors are printed and ensuing aborts taken through an incredible variety of functions, some of which print, some of which throw things meant to be printed, some of which apparently do both, some of which allow position reporting (others don't). There's also a whole second variety of functions for random prints that don't directly cause failure. This should all get systematized; we ought to have one function for panics and a small number more for messages of various types and severities, all defined in one place, and everything should use only those functions.
This offers a whole range of benefits, not limited to:
Interconnected with #2128. Also more or less a prerequisite for #2075.
The text was updated successfully, but these errors were encountered: