diff options
| author | bors <bors@rust-lang.org> | 2019-06-14 09:39:17 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-06-14 09:39:17 +0000 |
| commit | e699ea096fcc2fc9ce8e8bcf884e11496a31cc9f (patch) | |
| tree | 39efd442986e401b1660ffe94258b39cd5e177fd /src/etc/cpu-usage-over-time-plot.sh | |
| parent | 42503d57907ca13e062ee614b1753ab818c7b016 (diff) | |
| parent | 7a3184a04c4023d9ab93fe793c0d0ffb5e91240b (diff) | |
| download | rust-e699ea096fcc2fc9ce8e8bcf884e11496a31cc9f.tar.gz rust-e699ea096fcc2fc9ce8e8bcf884e11496a31cc9f.zip | |
Auto merge of #61679 - zackmdavis:maybe_dont_indicate_the_anonymous_lifetime, r=oli-obk
in which we decline to suggest the anonymous lifetime in declarations The elided-lifetimes-in-path lint (part of our suite of Rust 2018 idiom lints which we are hoping to promote to Warn status) was firing with an illegal suggestion to write an anonymous lifetime in a struct/item declaration (where we don't allow it). The linting code was already deciding whether to act on the basis of a `ParamMode` enum, indicating whether the present path-segment was part of an expression, or anywhere else. The present case seemed to be part of the "anywhere else", and yet meriting different rules as far as the lint was concerned, so it seemed expedient to introduce a new enum member. We yank out `TyKind::Path` arm into its own method so that we can call it with our new `ParamMode` specifically when lowering struct fields—one would have hoped to think of something more elegant than this, but it definitely beats changing the signature of `lower_ty` to take a `ParamMode`! Resolves #61124. cc @memoryruins r? @oli-obk
Diffstat (limited to 'src/etc/cpu-usage-over-time-plot.sh')
0 files changed, 0 insertions, 0 deletions
