# Subteam reports 2016-02-12 **URL:** \ **Category:** announcements\ **Created:** [February 12, 2016, 11:08pm UTC](https://internals.rust-lang.org/t/subteam-reports-2016-02-12/3175 "2016-02-12T23:08:38Z")\ **Posts on this page:** 3\ **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:** [February 12, 2016, 11:08pm UTC](https://internals.rust-lang.org/t/subteam-reports-2016-02-12/3175/1 "2016-02-12T23:08:39Z")
### Community [Full report](https://github.com/rust-lang/subteams/blob/master/community/reports/2016-02-12.md) **This week’s friend of the tree is Jeffrey Seyfried (@jseyfried)!** Jeffrey Seyfried (@jseyfried) has made some awesome contributions to name resolution. He has fixed a ton of bugs, reported previously unknown edge cases, and done some big refactorings, all of which have helped improve a complex and somewhat neglected part of the compiler. #### Rust OSCON activity There are 4 Rust-related talks accepted for [OSCON this May, in Austin](http://conferences.oreilly.com/oscon/open-source-us/): - [Emily Dunham’s “How to Learn Rust”](http://conferences.oreilly.com/oscon/open-source-us/public/schedule/detail/49024). - [Ben Striegel’s “Fearless Systems Programming for the Modern Developer”](http://conferences.oreilly.com/oscon/open-source-us/public/schedule/detail/49932). - [Steve Klabnik’s “Learn Rust”](http://conferences.oreilly.com/oscon/open-source-us/public/schedule/detail/49862). - [Josh Matthews’s “Optimizing Your Project for Contribution”](http://conferences.oreilly.com/oscon/open-source-us/public/schedule/detail/49310), though it’s not Rust-specific. ### Compiler [Full report](https://github.com/rust-lang/subteams/blob/master/compiler/reports/2016-02-12.md) No firm decisions were reached, but we discussed two topics of general interest: - RFCs [#1477](https://github.com/rust-lang/rfcs/pull/1477) and [#1478](https://github.com/rust-lang/rfcs/pull/1478), which discuss the intrinsics for doing atomic operations. At issue is what the behavior ought to be in the case of attempting to use the intrinsics with unsupported types – the current behavior is an LLVM abort, which seems suboptimal. - [Whether or not to support MIR plugins](https://internals.rust-lang.org/t/mir-compiler-plugins-for-custom-mir-passes/3166). Preliminary support landed in a recent PR, but it’s unclear if we will ever want to support MIR plugins long-term (and it’s certainly too early to offer even the faintest of stability promises). – nmatsakis ### Lang [Full report](https://github.com/rust-lang/subteams/blob/master/lang/reports/2016-02-12.md) “If you choose not to decide, you still have made a choice.” – Rush This week we decided to postpone two RFCs that have been lingering in final comment period for some time: - [RFC #1129](https://github.com/rust-lang/rfcs/pull/1129), which added a special overload for `map[key] = value` syntax. There were [concerns](https://github.com/rust-lang/rfcs/pull/1196#issuecomment-162044985) about the implementation complexity and the general proliferation of ways to insert into maps, particularly if [emplacement syntax](https://github.com/rust-lang/rfcs/pull/1228) becomes more mainstream. Hence we decided to postpone until we’ve had a chance to push harder on emplacement syntax. - [RFC #1196](https://github.com/rust-lang/rfcs/pull/1196), which allowed eliding type parameters and which filled in the results with `_`. Here the [concerns](https://github.com/rust-lang/rfcs/pull/1196#issuecomment-162044985) were about the interaction with the inference fallbacks that were described in [RFC 213](https://github.com/rust-lang/rfcs/blob/master/text/0213-defaulted-type-params.md) (but never fully implemented). [The decision](https://github.com/rust-lang/rfcs/pull/1196#issuecomment-183438534) was to postpone the RFC in favor of a broader discussion that tries to capture the full set of constraints. –nmatsakis PS. Do not interpret that opening quote as suggesting any sort of endorsement of the band Rush, official or otherwise. ### Libs [Full report](https://github.com/rust-lang/subteams/blob/master/libs/reports/2016-02-12.md) We had a busy week! RFC decisions: - [FCP PR #1415](https://github.com/rust-lang/rfcs/pull/1415): RFC: Deprecate type aliases in std::os::\*::raw - [FCP PR #1353](https://github.com/rust-lang/rfcs/pull/1353): Add retain\_mut to Vec and VecDeque We are moving a large number of RFCs into **final comment period** : - [FCP PR #1218](https://github.com/rust-lang/rfcs/pull/1218): RFC: Checked integer conversions - This RFC has stalled to some degree, but covers important ground; please help us finalize the design! - [FCP PR #1258](https://github.com/rust-lang/rfcs/pull/1258): Add macros to get the values of configuration flags - [FCP PR #1353](https://github.com/rust-lang/rfcs/pull/1353): Add retain\_mut to Vec and VecDeque - We’re close on this one, modulo bikeshedding on the final name. - [FCP PR #1393](https://github.com/rust-lang/rfcs/pull/1393): Expand `try!` macro with additional case - This RFC and the next both touch on the `try!` macro, and we likely want to postpone action here now that the [`?`/`catch` RFC](https://github.com/rust-lang/rfcs/pull/243) has been merged. - [FCP PR #1394](https://github.com/rust-lang/rfcs/pull/1394): Add `maybe!` macro equivalent to `try!` - [FCP PR #1419](https://github.com/rust-lang/rfcs/pull/1419): Safe memcpy for slices ([T]::copy\_from) - Some discussion about [`Copy` vs `Clone`](https://internals.rust-lang.org/t/assuming-clone-clone-is-equivalent-to-copy-semantics-for-all-instances-of-copy/3148?) that could potentially change the situation for this RFC. - [FCP PR #1443](https://github.com/rust-lang/rfcs/pull/1443): Extend atomic compare\_and\_swap - [FCP PR #1461](https://github.com/rust-lang/rfcs/pull/1461): Move some net2 functionality into libstd - We’ve had no feedback here in a month – please take a look! - [FCP PR #1467](https://github.com/rust-lang/rfcs/pull/1467): Stabilize volatile read and write We also reached a few decision on outstanding PRs and issues, as usual. ### Tools [Full report](https://github.com/rust-lang/subteams/blob/master/tools/reports/2016-02-12.md) The past few weeks saw the merging of [RFC 1361](https://github.com/rust-lang/rfcs/blob/master/text/1361-cargo-cfg-dependencies.md) which will improve the target-specific dependencies syntax in Cargo. Additionally, lots of effort has ramped up on the [multirust-rs](https://github.com/Diggsey/multirust-rs) project in preparation for it taking over `multirust.sh` as well as `rustup.sh`. Notable Rust PRs: - Support for MIPS MUSL [has landed](https://github.com/rust-lang/rust/pull/31298). - Backtrace support on MSVC [has been improved](https://github.com/rust-lang/rust/pull/31319). - Initial support for Illumos [has landed](https://github.com/rust-lang/rust/pull/31078). - Initial support for emscripten [has landed](https://github.com/rust-lang/rust/pull/31078), and ongoing PRs are happening to get more tests passing. - Rustdoc [will now display](https://github.com/rust-lang/rust/pull/30686) `since` to show when APIs first became available. - The beginnings of a new build system based on Cargo [have landed](https://github.com/rust-lang/rust/pull/31123). - The compiler flag `-C link-dead-code` [was added](https://github.com/rust-lang/rust/pull/31368) to aid in generating coverage information. Notable Cargo PRs: - The default build target [can now be set](https://github.com/rust-lang/cargo/pull/2335) through `build.target` in `.cargo/config`. - The `cargo metadata` subcommand [gained a `--no-deps` flag](https://github.com/rust-lang/cargo/pull/2359) to eventually replace `cargo read-manifest`. - Cargo on Windows [will now ensure](https://github.com/rust-lang/cargo/pull/2370) that child processes (tests, rustc, etc) will die when Cargo dies (e.g. via ctrl-c) ---
**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:** [February 13, 2016, 2:44am UTC](https://internals.rust-lang.org/t/subteam-reports-2016-02-12/3175/2 "2016-02-13T02:44:09Z")
One thing that was missed in the lang team report: the [`let`/`else` RFC](https://github.com/rust-lang/rfcs/pull/1303) is going into final comment period this week as well! ---
**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-02-12/3175/3 "2019-03-25T08:25:47Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.