"there seems to be very little gained by defining hierarchies of errors wrapping other errors." https://dwrensha.github.io/capnproto-rust/2016/01/11/async-rpc.html (great rust post)
miniblog.
Related Posts
https://elm-lang.org/news/compiler-errors-for-humans mentions the importance of layout and paragraphs for compile error messages.
Perhaps tools should do line wrapping if the terminal is very wide? It's definitely more comfortable to read.
Today in aggravating edge cases: difftastic would crash when line-wrapping content where Unicode combining characters occurred on the boundary. Argh.
> try wrapping the expression in `summary::FileContent::Text`
This rust-analyzer feature amazed me. I'd changed an API from taking a &str to a Text(String) and it offered a quick fix to correct the call sites!