# 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:** 57

<div class="post-metadata">

**Author:** ![vitiral](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/vitiral/32/2955_2.png) [@vitiral](https://internals.rust-lang.org/u/vitiral)\
**Post date:** [September 2, 2016, 12:31am UTC](https://internals.rust-lang.org/t/setting-our-vision-for-the-2017-cycle/3958/57 "2016-09-02T00:31:44Z")

</div>

One thing that could be improved with `#[no_std]` is getting some of the core crates (like [alloc](https://doc.rust-lang.org/alloc/)) stabilized.

I’m a little confused about that one in particular – are we likely to be changing `alloc::heap::allocate` in the future? It seems pretty basic to me.

---

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