Nominated (I-nominated) issues
Tracking Issue for RFC 213: Default Type Parameter Fallback (#27336)
Tracking issue for `cell_extras` stabilization (#27746)
- Added I-nominated. By @aturon
Tracking issue for make_ascii_{upper,lower}case (#27809)
- Added I-nominated. By @alexcrichton
Tracking issue for `braced_empty_structs` (RFC 218) (#29720)
Warn must_use in tuple (#29815)
Move Duration to libcore (and remove deprecated Duration::span) (#30594)
Nightly does not work on some Debian Wheezy because gcc doesn't support gold. (#30783)
Linking with gold does not search /usr/local/lib (#30784)
Don't make atomic loads and stores volatile (#30962)
DragonflyBSD build is broken (#31009)
- Added I-nominated. By @brson
rustc wrongly reports conflicting trait implementations (#31115)
- Added I-nominated. By @huonw
triage: I-nominated T-lang
I don’t have time to really dig into it, but I suspect the bug here might be that the associated type version does compile (although the two examples are fairly different: the second one only has three traits but the first one has 4?). Rust tries to avoid reasoning about implementations that don’t exist, unless it absolutely has to (which is what the
#[fundamental]attribute does, see e.g. https://dxr.mozilla.org/rust/rev/c14b615534ebcd5667f594c86d18eebff6afc7cb/src/libcore/marker.rs#60 and https://dxr.mozilla.org/rust/rev/c14b615534ebcd5667f594c86d18eebff6afc7cb/src/libcore/ops.rs#1637), because doing this reasoning is a pretty large backwards compatibility risk.cc @rust-lang/lang, but especially @nikomatsakis
In cross-compiled i686->x86_64 code, thread::spawn crashes on my system (#31139)
- Added I-nominated. By @alexcrichton
triage: I-nominated
Resolve: stop requiring `use` and `extern crate` declarations to precede statements in blocks (#31144)
Linking regression in 1.6 (#31150)
- Added I-nominated. By @brson
Windows linker regression in 1.6 (#31151)
- Added I-nominated. By @brson
Massive compiler perf regression (#31157)
- Added I-nominated. By @sfackler
Allow enum variants to be used through a type alias of the enum (#31179)
Beta-nominated issues
std: Stabilize custom hasher support in HashMap (#31081, open)
1.7 release notes (#31099, open)
mk: Move from `-D warnings` to `#![deny(warnings)]` (#31120, open)
implement RFC amendment 1462 (add `[` to FOLLOW(ty)) (#31152, open)
Remaining issues
std::io::Take should have into_inner() method (#23755)
- Added P-medium. By @alexcrichton
triage: P-medium
@sfackler indicated that he was interested in making a PR for this and limiting it to the I/O adaptors for now.
Box::from(&str) -> Box regression (#30634)
- Added beta-nominated. By @brson
- Removed beta-nominated. By @brson
librustc_trans: function parameters should be annotated with zeroext/signext (#30841)
- Added I-nominated. By @Aatch
- Added P-medium. By @nikomatsakis
triage: P-medium
Good catch reporting this bug! This should definitely be fixed, but PowerPC is not a “tier 1” platform, so it’s not a high priority (drop everything) sort of bug.
Undocumented panics in std::process on unix for strings with interior nuls (#30858)
- Added P-medium. By @alexcrichton
triage: P-medium
The libs team discussed this in triage yesterday and the conclusion was that the defer-the-error strategy is fine for
Command. We discussed briefly that this may be altering the contract ofCommand(e.g. changing panics to results), but theResultbehavior seems more consistent with thestd::fsAPIs.
BufWriter is not panic-safe (#30888)
- Added P-medium. By @alexcrichton
triage: P-medium
@sfackler is fixing the data corruption in #31068
Compilation error in Rust 1.6 stable (#31118)
- Added I-nominated. By @brson