Tracking issue for https://github.com/rust-lang/rfcs/pull/809. This should be filled out with TODO items. Note that in this case there are some [unsettled design questions](https://github.com/rust-lang/rfcs/pull/809#issuecomment-73910414) to be resolved as well. To do: - [x] land placement-`in` desugaring implementation - [ ] land overloaded-`box` desugaring implementation - [ ] port `libstd` APIs to support `in` - [ ] port `libstd` APIs to support `box` - [ ] resolve/finalize syntax for placement-`in` - [ ] investigate improvement of inference, coercion, and cast interactions (subissues #22221, #22403, #22405) - [ ] improve error messages when code is rejected (#22231) Unresolved questions: - [ ] best precedence for `box` (was https://github.com/rust-lang/rust/issues/21192)
Tracking issue for rust-lang/rfcs#809. This should be filled out with TODO items. Note that in this case there are some unsettled design questions to be resolved as well.
To do:
indesugaring implementationboxdesugaring implementationlibstdAPIs to supportinlibstdAPIs to supportboxin_inexpr as Box<_>when expectingBox<Trait>? #22221, Cannot dox as Box<[T]>forx: Box<[T; k]>#22403, Could type inference insert coercions to accommodate box desugaring? #22405)Unresolved questions:
box(was Precedence ofboxis possibly wrong #21192)