]> git.lizzy.rs Git - rust.git/commit
Revise the `const_nonmatching` flag with more info about author's intent.
authorFelix S. Klock II <pnkfelix@pnkfx.org>
Sat, 5 Jul 2014 06:04:07 +0000 (08:04 +0200)
committerFelix S. Klock II <pnkfelix@pnkfx.org>
Fri, 11 Jul 2014 15:01:01 +0000 (17:01 +0200)
commit5d1bdc320ba5304854f409ba68060f5739bca044
treed78792d061994803dba9454a134a59829f8cf0fb
parentc9a77d03ddc0b949eabee4b1f25edcf3b9e1251c
Revise the `const_nonmatching` flag with more info about author's intent.

In particular, I want authors of deriving modes to understand what
they are opting into (namely quadratic code size or worse) when they
select NonMatchesExplode.
14 files changed:
src/libsyntax/ext/deriving/clone.rs
src/libsyntax/ext/deriving/cmp/eq.rs
src/libsyntax/ext/deriving/cmp/ord.rs
src/libsyntax/ext/deriving/cmp/totaleq.rs
src/libsyntax/ext/deriving/cmp/totalord.rs
src/libsyntax/ext/deriving/decodable.rs
src/libsyntax/ext/deriving/default.rs
src/libsyntax/ext/deriving/encodable.rs
src/libsyntax/ext/deriving/generic/mod.rs
src/libsyntax/ext/deriving/hash.rs
src/libsyntax/ext/deriving/primitive.rs
src/libsyntax/ext/deriving/rand.rs
src/libsyntax/ext/deriving/show.rs
src/libsyntax/ext/deriving/zero.rs