# Setting our vision for the 2017 cycle

**URL:** <https://internals.rust-lang.org/t/setting-our-vision-for-the-2017-cycle/3958>\
**Category:** Uncategorized\
**Created:** [September 1, 2016, 6:03pm UTC](https://internals.rust-lang.org/t/setting-our-vision-for-the-2017-cycle/3958 "2016-09-01T18:03:07Z")\
**Posts on this page:** 1\
**Showing post:** 30

<div class="post-metadata">

**Author:** ![kornel](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/kornel/32/2711_2.png) [@kornel](https://internals.rust-lang.org/u/kornel)\
**Post date:** [September 1, 2016, 8:29pm UTC](https://internals.rust-lang.org/t/setting-our-vision-for-the-2017-cycle/3958/30 "2016-09-01T20:29:15Z")

</div>

In terms of compiler errors, currently linker errors are the weakest. It’s just “we ran this unreadable long command and something didn’t work”.

I know it’s probably hard to fix, and it’s not rustc, but the rest of the toolchain, but still — these errors happen, and it’s often hard to figure out why.

---

_[View the full topic](https://internals.rust-lang.org/t/setting-our-vision-for-the-2017-cycle/3958)._
