starkat99

In response to Rust's call for blogs about Rust development in 2020, here's a few of my own thoughts:

1. Improve Error ergonomics

For the love of all that is good about Rust, Error is *still* the single biggest pain-point when dealing with Rust.
Things are drastically improved with some of the changes to the Error trait, but it's still really unclear what 
the best way to deal with Error types for Rust. The old failure or error-chain crates have been abandoned, yet they're
still widely used in libraries. It's just still too difficult and there's not standardized way for a library to
easily create Error types (even error derive crates don't really seem to get things right imo), or for apps to
handle a bunch of different types of them easily. I know I often just end up with a lot of functions using