More robust error handling in Rope

Question

More robust error handling in Rope

Opened this issue 8 years ago · 2 comments

Right now, a lot of our Rope code is littered with panic!()s and .expect()s. This is fine for a first iteration, but we need to move toward more robust error handling. At the very least, we should replace as many panics as possible with Results.

Answer 1 · 2017-01-03T17:53:58.000Z

We might want to look into using the brson/error-chain crate. I have no experience using this, but I hear it's good.

See also: http://brson.github.io/2016/11/30/starting-with-error-chain

Answer 2 · 2017-01-03T17:56:03.000Z

Some questions:

what do libraries need to do to to support error-chain? is it only for executables?
can we support error-chain as an optional dependency in a library?