In this week’s meeting, we promoted two RFCs to FCP:
RFC 1492 proposes to permit
..notation in patterns as a more general replacement to
_, so that one can write a pattern like
Foo(x, ..)instead of
Foo(x, _, _, _).
RFC 1592 is a small amendment that corrects an oversight in the
original well-formedness RFC, by making tuples require that all
elements except for the last element be
Sized(just as structs do).
In addition, RFC 1358 remains in FCP for another week as we discuss the precise interaction between custom alignment and packed structs. It seems that there is a difference in behavior between MSVC and GNU and it’s not entirely clear which behavior to adopt.
This week the libs team discussed the set of issues that were going to move into their cycle-long final comment period for either stabilization or deprecation. The following issues will all be decided on at the end of the cycle, and please feel free to leave comments on them!
- FCP Issue #27717: Tracking issue for static synchronization primitives
- FCP Issue #27720: Tracking issue for OpenOptionsExt on Windows
- FCP Issue #27784: Tracking issue for char encoding methods
- FCP Issue #30014: Tracking issue for OpenOptions expansion
FCP Issue #30425:
Tracking issue for
downgraded_weak(No way to construct std::rc::Weak without a strong reference)
- FCP Issue #30449: Custom panic handlers in the standard library
- FCP Issue #31190: Tracking issue for CStr::from_bytes_with_nul
- FCP Issue #31399: Tracking issue for SystemTime accessors from fs::Metadata
- FCP Issue #31767: Tracking issue for compare_exchange
- FCP Issue #32111: Tracking issue for the Peekable::is_empty function
- FCP Issue #32281: Add methods exposing keys of BTreeMap and HashMap entries
- FCP Issue #32312: Tracking issue for Unix Sockets in the standard library
FCP Issue #32551:
- FCP Issue #33018: Tracking issue for slice::binary_search_by_key