Subteam report: lang 2015-07-09
Dashboard
It's been a few weeks since the last report. To be honest, though, there hasn't been a lot of action in the language subteam, due to the Mozilla work week, some vacations, and other factors.
This week, we'd like to move RFC #1150 into FCP:
- FCP PR #1150: Allow
re-exporting associated items with
use.
This PR #873 about macros in types will remain in FCP for one more week due to the fact that there was no time yet to talk it over in depth. However, this will be the last week, or I will eat my hat (or something):
- FCP PR #873: Allow macros in types. There has been some discussion but no firm decision was reached.
Finally, the other RFC that was in FCP, #756, has been withdrawn. The topic was expanded sugar for closure expressions, and the judgement was that there wasn't sufficient motivation to make the change at this time. Perhaps later.
--- nmatsakis
RFC phase
- PR #197:
ManuallyDroptype gives precise control of dtors of inline data. - PR #243: Trait-based exception handling
- PR #638: Specify unwinding
- PR #733: Amend macro future proofing RFC
- PR #890: RFC: Custom preludes
- PR #953:
overloaded assignment operations
a += b - PR #1062: Constants that depend on type parameters in generic code
- PR #1129:
IndexAssign: overloading the
a[b] = cexpression - PR #1135: Implement raw fat pointer comparisons
- PR #1148: Mutually exclusive traits
- PR #1150:
RFC: Allow re-exporting associated items with
use - PR #1154: Disjoins (anonymous enums)
- PR #1168:
Make
sizean associated constant - PR #1177: Anonymous/placeholder lifetime "'_".
- PR #1180:
Propose
Interior<T>data-type, to allow moves out of the dropped value during the drop hook. - PR #1183: RFC: Allow changing the default allocator
- PR #1189: 0401: misc improvements
- PR #1190: Style: function declarations
- PR #1192: RFC for inclusive ranges with ...
- FCP PR #756:
Allow closure expressions to expand to a
&or&muttemporary - FCP PR #873: Allow macros in types
Implementation phase
High priority issues
- Issue #24622: Mismatched assumptions for interaction between associated type and lifetime in trait
- Issue #25310:
Passing a
Fnto anfnnow requires explicit lifetimes for theFnand all references passed to it when invoked - Issue #25658:
In macros,
$($x:expr),*fragments can be used to bypass future-proofing restrictions - Issue #25860: Implied bounds on nested references + variance = soundness hole
- Issue #26279: nightly rustc breaks stable code for some type inferences
- Issue #26739: In macros, expr followed by { is buggy
- Issue #26775: 'pub extern crate' is accepted and behaves badly
- Issue #26813: Regression on beta for trait bounds on supertrait's associated items