about summary refs log tree commit diff
path: root/src/rustllvm/RustWrapper.cpp
diff options
context:
space:
mode:
authorZack M. Davis <code@zackmdavis.net>2018-04-15 11:12:33 -0700
committerZack M. Davis <code@zackmdavis.net>2018-04-15 11:12:33 -0700
commite77110e1f61e42c0f0e9e3288edb0d663eb39bba (patch)
tree2207510db186e1690b92d724f0f60ba23d7db3b2 /src/rustllvm/RustWrapper.cpp
parent7360d6dd678d186d9c9b46311b75ba6840e61aa2 (diff)
downloadrust-e77110e1f61e42c0f0e9e3288edb0d663eb39bba.tar.gz
rust-e77110e1f61e42c0f0e9e3288edb0d663eb39bba.zip
don't see issue #0
The unstable-feature attribute requires an issue (neglecting it is
E0547), which gets used in the error messages. Unfortunately, there are
some cases where "0" is apparently used a placeholder where no issue
exists, directing the user to see the (nonexistent) issue #0. (It would
have been better to either let `issue` be optional—compare to how issue
is an `Option<u32>` in the feature-gate declarations in
libsyntax/feature-gate.rs—or actually require that an issue be created.)
Rather than endeavoring to change how `#[unstable]` works at this time
(given competing contributor and reviewer priorities), this simple patch
proposes the less-ambitious solution of just not adding the "(see
issue)" note when the number is zero.

Resolves #49983.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions