Subteam report: lang 2015-07-24

Dashboard

Two decisions were made since the last report:

One RFC is entering final comment period:

RFC #1219: extending the use syntax to allow renaming in group imports.
RFC #1214: clarifying rules for projections and well-formedness. This is a soundness RFC that clarifies some of the language rules, closing various soundness issues in the process. Some existing code may no longer compile (full evaluation in progress); in any case, the plan is to phase the changes in gradually.

Finally, we would like to call attention to one pending RFCs:

RFC #1177: introducing an anonymous placeholder lifetime '_. There are some debates as to the best defaulting behavior and best syntax; more input would be helpful.

Thanks!

--- nmatsakis

PR #197: ManuallyDrop type 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] = c expression
PR #1135: Implement raw fat pointer comparisons
PR #1148: Mutually exclusive traits
PR #1154: Disjoins (anonymous enums)
PR #1168: Make size an 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 #1189: 0401: misc improvements
PR #1190: Style: function declarations
PR #1192: RFC for inclusive ranges with ...
PR #1196: RFC for allowing eliding more type parameters.
PR #1199: SIMD groundwork
PR #1201: Add support for naked functions.
PR #1209: Update FOLLOW set for ty tokens
PR #1210: RFC: impl specialization
PR #1214: [RFC] Clarify (and improve) rules for projections and well-formedness
PR #1216: Promote ! to a type.
PR #1219: use_group_as RFC
FCP PR #1183: RFC: Allow changing the default allocator

Issue #24622: Mismatched assumptions for interaction between associated type and lifetime in trait
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 #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
Issue #26952: Stable regression in nightly
Issue #27060: repr(packed) allows invalid unaligned loads