Subteam report: lang 2015-09-04

Highlights

It's been a busy week this week! First off, we accepted a number of RFCs:

We also moved a number of RFCs to final comment period:

RFC #1199 -- SIMD groundwork, which describes a flexible set of intrinsics that enable SIMD computation. These intrinsics are not intended to be used directly; rather, they are meant to be a foundation for third-party packages. See also Huon's excellent blog post on the topic.
RFC #1224 -- RFC process, which helps to clarify when an RFC is needed.
RFC #1237 -- clarify operator behavior in extreme conditions, which amends the overflow RFC with some more specifics documenting various bits of the implementation.
RFC #1238 -- nonparametric dropck, which reverts some of the more subtle aspects of the current dropck rules, helping to restore soundness and pave the way for specialization.
RFC #1240 -- creating references into #[repr(packed)] structs should be unsafe, as they can violate alignment requirements and cause crashes.

Thanks!

-- nmatsakis

PR #197: ManuallyDrop type gives precise control of dtors of inline data.
PR #243: Trait-based exception handling
PR #733: Amend macro future proofing RFC
PR #1062: Constants that depend on type parameters in generic code
PR #1129: IndexAssign: overloading the a[b] = c expression
PR #1148: Mutually exclusive traits
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 #1190: Style: function declarations
PR #1196: RFC for allowing eliding more type parameters.
PR #1210: RFC: impl specialization
PR #1228: Place left arrow syntax (place <- expr)
PR #1237: clarify extreme operator behaviour
PR #1245: Amend #911 const-fn to allow unsafe const functions
PR #1248: Safe intrinsics RFC
PR #1258: Add macros to get the values of configuration flags
PR #1260: RFC: Allow a re-export for main
PR #1268: Allow overlapping implementations for marker traits
FCP PR #1199: SIMD groundwork
FCP PR #1224: Update the RFC process with sub-teams, amongst other things.
FCP PR #1238: Nonparametric dropck
FCP PR #1240: References into repr(packed) structs should be unsafe.

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 #26438: Tracking issue for Adjust default object bounds (RFC 1156)
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 #27060: repr(packed) allows invalid unaligned loads

Issue #26502: Do not warn about unused arguments in default methods
Issue #27499: Use different numbers of #s when expanding documentation comments
Issue #27972: Allow where clauses involving types which don't include a type parameter.
Issue #28160: Settle execution order uncertainty for +=