about summary refs log tree commit diff
path: root/src/test/debuginfo/enum-thinlto.rs
diff options
context:
space:
mode:
authorZack M. Davis <code@zackmdavis.net>2018-04-02 19:34:52 -0700
committerZack M. Davis <code@zackmdavis.net>2018-04-09 08:53:30 -0700
commita1d90a2a2a2d3ff6843d8fca17be4819dba9ab6b (patch)
tree8a1fcba08ab73212011884d72dc1d156ef548772 /src/test/debuginfo/enum-thinlto.rs
parent4b9b70c394e7f341b4016fce4cbf763d404b26f9 (diff)
downloadrust-a1d90a2a2a2d3ff6843d8fca17be4819dba9ab6b.tar.gz
rust-a1d90a2a2a2d3ff6843d8fca17be4819dba9ab6b.zip
in which the non-shorthand patterns lint keeps its own counsel in macros
In issue #49588, Michael Lamparski pointed out a scenario in which the
non-shorthand-field-patterns lint could be triggered by a macro-expanded
pattern, in a way which was direly unwieldy for the macro author to guard
against and unreasonable to expect the macro user to take into account. We can
avoid this by not linting patterns that come from macro-expansions. Although
this entails accepting "false negatives" where the lint could genuinely improve
macro-templated code, avoiding the reported "true-but-super-annoying positive"
may be worth the trade? (Some precedent for these relative priorities exists as
no. 47775 (5985b0b0).)

Resolves #49588.
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions