Library stabilizations for the 1.9 release

[alexcrichton]

Another cycle, another release, more final comment periods! The libs team discussed this past triage meeting what APIs should be stabilized for the 1.9 release on May 26, 2016. This is a pretty exciting list of APIs with lots of goodies! Each issue has entered a cycle-long final comment period for discussion about the API being stabilized. If you’ve got reservations or want to show support, please feel free to do so by commenting on the issues!

• panic::recover - stabilize
• std::raw - deprecate the slice-related bits
• the str_char feature - mixture of stabilization/deprecation
• ptr::as_ref - stabilization pending a good name
• char encoding methods - stabilization with a tweaked API
• ascii into methods - needs discussion
• CommandExt::session_leader - deprecate
• utf-16 decoding iterators - stabilize
• set recovery methods - stabilize
• OsString capacity/length methods - stabilize
• pthread_t from JoinHandle - stabilize (but some open questions)
• the #[deprecated] attribute - stabilize
• OpenOptions::create_new - stabilize (but some open questions)
• panic::propagate - stabilize
• getting hashers from HashMap and HashSet - stabilize
• CommandExt::{exec, before_exec} - stabilize, maybe before_exec too
• File::try_clone - stabilize
• SocketAddr::set_* methods - stabilize
• copy_from_slice - stabilize
• ptr::{read,write}_volatile - stabilize pending an LLVM assertion fix

[dhardy]

Any chance we could see stabilisation of HashSet's get, replace and take methods? I’ve been using them in hashindexed for a while.

[burntsushi]

Yup, that’s up for FCP this round under “set recovery methods”: https://github.com/rust-lang/rust/issues/28050

[alexcrichton]

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.