# \[lang-team-minutes\] feature status report: placement in and box

**URL:** <https://internals.rust-lang.org/t/lang-team-minutes-feature-status-report-placement-in-and-box/4646>\
**Category:** language design\
**Created:** [January 23, 2017, 3:14pm UTC](https://internals.rust-lang.org/t/lang-team-minutes-feature-status-report-placement-in-and-box/4646 "2017-01-23T15:14:54Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![hanna-kruppe](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/hanna-kruppe/32/6540_2.png) [@hanna-kruppe](https://internals.rust-lang.org/u/hanna-kruppe)\
**Post date:** [February 11, 2017, 9:29pm UTC](https://internals.rust-lang.org/t/lang-team-minutes-feature-status-report-placement-in-and-box/4646/12 "2017-02-11T21:29:12Z")

</div>

For `box EXPR`/`Box::new`, that _may_ be possible, but it would have to be a rather ad-hoc, magical attribute. And it would presumably come with some weird rules for the implementation of `new` to guarantee that the optimization actually applies (remember that this is intended to apply not just to `Box` but also to `Rc`, `Arc`, and third-party types). So I doubt whether that feature would actually be easier to implement or less of an addition to the language. Then there’s the fact that `box EXPR` is simple more ergonomic, and nicely matches `box` _patterns_ which are desirable too.

With “placement in” syntax, e.g. as replacement for ~~`Vec::new`~~ ( **edit:** `Vec::push`, sorry for the confusion), it’s not really possible to avoid new syntax, see [this old FAQ](https://internals.rust-lang.org/t/placement-nwbi-faq-new-box-in-left-arrow/2789) (particularly question #4).

---

_[View the full topic](https://internals.rust-lang.org/t/lang-team-minutes-feature-status-report-placement-in-and-box/4646)._
