Hacker News new | past | comments | ask | show | jobs | submit login

Things that have changed:

- NLL (non lexical lifetimes) are now in stable, so working with lifetimes and references is a bit easier

- stack traces: failure is still around, it's got a fairly large group using it, it seems. I prefer the std error handling route most times.

- async is hard: it's still pretty hard




Unfortunately failure and errorchain appear to not be cool anymore (ie I've noticed quite a few people are migrating away from failure just like they did from errorchain) and there doesn't appear to be any push from the Rust team as of yet.

I think it's a serious problem as your code base grows and I wish we had some more work on the RFC front.


Given the vanilla error handling is my favorite of the lot, I don't really consider it a bad thing that people are moving away from it.

There are some downsides, like the lack of stack traces, but it's a nice pattern. Does it have to be 'one size fits all'?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: