Skip to content
This repository has been archived by the owner. It is now read-only.

/subteams

Permalink
Branch: master
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
348 lines (326 sloc) 17.7 KB
Raw Blame History

Subteam report: libs 2015-08-14

Highlights

Starting with the current release cycle (for 1.4), we are making some changes to the stabilization process:

  • All unstable APIs now map to tracking issues. The APIs will be tagged with the issue tracking them, so when you get an error that you need a feature gate, the compiler can also tell you which issue to subscribe to for stabilization. We'll use these issues as a centralized place for discussing questions/concerns about APIs before they are stabilized.

  • Stabilization will be tied to our 6 week release cycles: at the beginning of the cycle, the team will announce a number of unstable features undergoing "final comment period" (heading either toward stabilization or deprecation). The comment period will last for the entire release cycle. One week before the release is cut, the team will make final decisions and land a PR accordingly.

This new process such give much more visibility into the feature pipeline and make the stabilization process easier to follow.

With that in mind, here are the features undergoing FCP for this cycle:

In addition, this week we made the following decisions:

  • FCP PR #1195: ordered query API
    • Close, with the hope that we can find a way to achieve these goals with a smaller API surface
  • FCP PR #1192: RFC for inclusive ranges with ...
    • Merge, with the extra field for Iterator being kept unstable for the time being.

Finally, the following RFC is entering FCP this week:

  • FCP PR #1198: pretty print Debug of tuples, tuple structs and enum variants in a single line

Dashboard

Stabilization phase

Implementation phase

  • Issue #19986: Tracking issue for collections reform part 2 (RFC 509)
  • Issue #21923: Audit raw pointer to reference conventions
  • Issue #22477: Tracking issue for Add a generic string pattern matching API (RFC 528)
  • Issue #23055: Tracking issue for Replace Vec::drain by a method that accepts a range parameter (RFC 574)
  • Issue #24263: discriminant_value intrinsic -- tracking issue for 639
  • Issue #27389: Allow changing the default allocator
  • Issue #27517: Add ByNeed and Predicate traits
  • Issue #27585: Tracking issue for read_exact (RFC #980)

Issues needing a decision

RFC phase

  • FCP PR #1192: RFC for inclusive ranges with ...
  • FCP PR #1194: RFC: Add item recovery collection APIs
  • FCP PR #1198: pretty print Debug of tuples, tuple structs and enum variants in a single line
  • PR #1036: Add Builder guidelines
  • PR #1100: Add thread-local custom panic handlers to customize the behavior of thread panics
  • PR #1147: Target Version
  • PR #1158: RFC: Expand the std::net module
  • PR #1168: Make size an associated constant
  • PR #1212: RFC: line-endings
  • PR #1218: RFC: Checked integer conversions
  • PR #1224: Update the RFC process with sub-teams, amongst other things.
  • PR #1233: RFC: Add Box::leak to leak Box to &'static mut T
  • PR #1235: More control over BufReader
  • PR #1236: RFC: Stabilize catch_panic
  • PR #1238: Nonparametric dropck
  • PR #1241: Forbid wildcard dependencies on crates.io
  • PR #1242: RFC: policy for rust-lang crates
  • PR #1252: Document and expand the open options
  • PR #1255: RFC: Stabilize OS string to bytes conversions

High priority issues
You can’t perform that action at this time.