# Subteam reports 2016-01-15 **URL:** \ **Category:** announcements\ **Created:** [January 15, 2016, 11:11pm UTC](https://internals.rust-lang.org/t/subteam-reports-2016-01-15/3089 "2016-01-15T23:11:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![aturon](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/aturon/32/3272_2.png) [@aturon](https://internals.rust-lang.org/u/aturon)\ **Post date:** [January 15, 2016, 11:11pm UTC](https://internals.rust-lang.org/t/subteam-reports-2016-01-15/3089/1 "2016-01-15T23:11:40Z")
### Lang [Full report](https://github.com/rust-lang/subteams/blob/master/lang/reports/2016-01-15.md) Three RFCs went into final comment period this week: - [RFC 243](https://github.com/rust-lang/rfcs/pull/243#issuecomment-172057844), which adds a `?` operator that is roughly equivalent to the existing `try!` macro, except that it operates in suffix position. The scope of the `?` operator can be controlled using a `try { ... }` block and there is also sugar for handling errors `try { .. } catch { .. }`. This RFC has been around since before 1.0, and has seen quite a lot of discussion. (Note that the `try` and `catch` keywords are [likely to change](https://github.com/rust-lang/rfcs/pull/243#issuecomment-164857624), given the overlap with the existing `try!` macro. - [RFC 1320](https://github.com/rust-lang/rfcs/pull/1320) which modifies the `RangeInclusive` type from a struct to an enum. - [RFC 1462](https://github.com/rust-lang/rfcs/pull/1462), which adds the open brace character to the follow set for type fragments. This macro is taking a “fast path” to FCP due to the time-sensitive nature of its contents – it is intended to mitigate the effects of a recent bugfix. We are seeking feedback on [the name and syntax for so-called OIBIT traits](https://internals.rust-lang.org/t/pre-rfc-renaming-oibits-and-changing-their-declaration-syntax/3086), such as `Send` and `Sync`. Finally, we’ve decided to accept [RFC 1331](https://github.com/rust-lang/rfcs/pull/1331), which spells out a procedure for making an official Rust grammar that is independent from the implementation. ### Libs [Full report](https://github.com/rust-lang/subteams/blob/master/libs/reports/2016-01-15.md) This week, we made decisions on all the outstanding FCP issues for Rust 1.7: - [FCP Issue #23284](https://github.com/rust-lang/rust/issues/23284): Tracking issue for Path::relative\_from stabilization - Stabilize (with renaming and slight type change) - [FCP Issue #27709](https://github.com/rust-lang/rust/issues/27709): Tracking issue for Ipv{4,6}Addr convenience methods - Stabilize subset of methods confirmed to match official spec - [FCP Issue #27712](https://github.com/rust-lang/rust/issues/27712): Tracking issue for `fs_mode` stabilization - Deprecate in favor of libc - [FCP Issue #27713](https://github.com/rust-lang/rust/issues/27713): Tracking issue for custom hashers in HashMap - Stabilize with renaming - [FCP Issue #27722](https://github.com/rust-lang/rust/issues/27722): Tracking issue for `path_prefix` stabilization - Deprecate - [FCP Issue #27728](https://github.com/rust-lang/rust/issues/27728): Tracking issue for formatting with a radix - Deprecate - [FCP Issue #27729](https://github.com/rust-lang/rust/issues/27729): Tracking issue for `as_slice` stabilization - Stabilize - [FCP Issue #27735](https://github.com/rust-lang/rust/issues/27735): Tracking issue for `IntoCow` stabilization - Deprecate - [FCP Issue #27739](https://github.com/rust-lang/rust/issues/27739): Tracking issue for `Zero`/`One`/`iter_arith` stabilization - [Punt](https://github.com/rust-lang/rust/issues/27739#issuecomment-172033338) - [FCP Issue #27750](https://github.com/rust-lang/rust/issues/27750): Tracking issue for `clone_from_slice` stabilization - Stabilize with new panic behavior - [FCP Issue #27753](https://github.com/rust-lang/rust/issues/27753): Tracking issue for `num_bits_bytes` stabilization - Deprecate - [FCP Issue #27755](https://github.com/rust-lang/rust/issues/27755): Tracking issue for `wrapping` stabilization - Stabilize inherent methods - [FCP Issue #27782](https://github.com/rust-lang/rust/issues/27782): Tracking issue for DebugTuple::formatter - Deprecate - [FCP Issue #27791](https://github.com/rust-lang/rust/issues/27791): Tracking issue for str escaping - [Punt](https://github.com/rust-lang/rust/issues/27791#issuecomment-172035085) - [FCP Issue #27798](https://github.com/rust-lang/rust/issues/27798): Tracking issue for sync::Semaphore - Deprecate - [FCP Issue #28796](https://github.com/rust-lang/rust/issues/28796): Tracking issue for FnBox() - [Punt](https://github.com/rust-lang/rust/issues/28796#issuecomment-171252018) - [FCP Issue #29157](https://github.com/rust-lang/rust/issues/29157): Tracking issue for owned CString conversions - Stabilize - [FCP Issue #30423](https://github.com/rust-lang/rust/issues/30423): Tracking issue for slice::sort\_by\_key - Stabilize Next week we return to our regular programming! ### Compiler [Full report](https://github.com/rust-lang/subteams/blob/master/compiler/reports/2016-01-15.md) We have decided to place [RFC 1457](https://github.com/rust-lang/rfcs/pull/1457) into final comment period. This RFC concerns the way that `for` loops are internally implemented in the compiler. ### Tools [Full report](https://github.com/rust-lang/subteams/blob/master/tools/reports/2016-01-15.md) - [Initial support for PNaCl](https://github.com/rust-lang/rust/pull/30401) is in the Makefiles - [The compiler itself now has rpath enabled by default](https://github.com/rust-lang/rust/pull/30353) to avoid requiring the usage of `LD_LIBRARY_PATH` for downloaded installers. - A patch to [use the gold linker by default](https://github.com/rust-lang/rust/pull/29974) landed, but it was [unfortunately reverted](https://github.com/rust-lang/rust/pull/30913) due to bugs - The compiler can now emit errors in [JSON format](https://github.com/rust-lang/rust/pull/30711) - Initial support for [powerpc64](https://github.com/rust-lang/rust/pull/30776) has landed. - The website has seen a [major revamp](https://www.reddit.com/r/rust/comments/40zxey/major_website_updates/). - The RFC for [Cargo target specific dependencies](https://github.com/rust-lang/rfcs/pull/1361) will remain in FCP for awhile longer as the syntax is hammered out a bit more. ---
**Author:** ![aturon](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/aturon/32/3272_2.png) [@aturon](https://internals.rust-lang.org/u/aturon)\ **Post date:** [March 25, 2019, 8:25am UTC](https://internals.rust-lang.org/t/subteam-reports-2016-01-15/3089/2 "2019-03-25T08:25:41Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.