# Crate evaluation for 2017-06-27: error-chain

**URL:** <https://internals.rust-lang.org/t/crate-evaluation-for-2017-06-27-error-chain/5362>\
**Category:** libs\
**Created:** [June 6, 2017, 8:30am UTC](https://internals.rust-lang.org/t/crate-evaluation-for-2017-06-27-error-chain/5362 "2017-06-06T08:30:27Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)\
**Post date:** [July 6, 2017, 1:04am UTC](https://internals.rust-lang.org/t/crate-evaluation-for-2017-06-27-error-chain/5362/25 "2017-07-06T01:04:36Z")

</div>

The libs team discussed this at last week’s meeting. It was a pretty productive meeting, and a lot of remediations fell out of it. We’ll get either @aturon or myself to file the bugs soon.

Some of the big resolutions were:

- lower the Error trait into probably the alloc crate so no\_std error-chain makes sense
- investigate a complete syntactic redesign to accommodate all the missing capabilities raised in the review. This will certainly require using some form of procedural macros. It may or may not be a 1.0 blocker

I’m uh, missing the etherpad link we used to take notes, so I hope somebody else has it.

---

_[View the full topic](https://internals.rust-lang.org/t/crate-evaluation-for-2017-06-27-error-chain/5362)._
