diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-10-28 21:36:02 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-28 21:36:02 +0100 |
| commit | d88723203581d7826ebe7ff2bffec76b05c30420 (patch) | |
| tree | de823b8c0ffd48b1f2e7cf00dfd9dc24d1e460d6 /src/libsyntax/parse/parser | |
| parent | 531240c626401a183c62553bc67ef3352efc0071 (diff) | |
| parent | 92b151287fcda73db8e95eeca8be97d66905626d (diff) | |
| download | rust-d88723203581d7826ebe7ff2bffec76b05c30420.tar.gz rust-d88723203581d7826ebe7ff2bffec76b05c30420.zip | |
Rollup merge of #65858 - davidtwco:rfc-2203-feature-gate-in-error, r=ecstatic-morse
suggest `const_in_array_repeat_expression` flag This PR adds a suggestion to add the `#![feature(const_in_array_repeat_expression)]` attribute to the crate when a promotable expression is used in a repeat expression and the feature gate is not enabled. Unfortunately, this ended up being a little bit more complex than I anticipated, which may not have been worth it given that this would all be removed when the feature is stabilized. However, with #65732 and #65737 being open, and the feature gate having not been being suggested to potential users, the feature might not be stabilized in a while, so maybe this is worth landing. cc @Centril (addresses [this comment](https://github.com/rust-lang/rust/pull/61749#discussion_r307863857)) r? @ecstatic-morse (opened issues related to RFC 2203 recently)
Diffstat (limited to 'src/libsyntax/parse/parser')
0 files changed, 0 insertions, 0 deletions