|
|
|
|
|
by dwattttt
410 days ago
|
|
I find myself working through a hierarchy of error handling maturity as a project matures. Initial proof of concepts just get panics (usually with a message). Then functions start to be fallible, by adding anyhow & considering all errors to still be fatal, but at least nicely report backtraces (or other things! context doesn't have to just be a message) Then if a project is around long enough, swap anyhow to thiserror to express what failure modes a function has. |
|