diff options
| author | kennytm <kennytm@gmail.com> | 2018-08-17 00:13:23 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-08-17 00:13:23 +0800 |
| commit | 4968eea6395f69df57274deeed473bbed853467b (patch) | |
| tree | 612bf34377f15cd942afb95a201febde0150ac55 /src/test/debuginfo/enum-thinlto.rs | |
| parent | 1cda84bfdbed2c14ae787cb41ebff1c166ac5fd9 (diff) | |
| parent | bc8cead070a44a9ebc7cd559479e0266c45c7c72 (diff) | |
| download | rust-4968eea6395f69df57274deeed473bbed853467b.tar.gz rust-4968eea6395f69df57274deeed473bbed853467b.zip | |
Rollup merge of #53364 - varkor:gat-warn-broken, r=pnkfelix
Warn if the user tries to use GATs GATs are currently broken, but still accessible behind a feature gate. This leads to people attempting to use them and then immediately encountering ICEs (or other broken behaviour). Here, we emit a warning if the user tries to use any feature associated with GATs, hopefully making it obvious that ICEs and the like are expected. For the meantime, this seems better than continually getting reported errors (for example: [here](https://github.com/rust-lang/rust/issues?q=is%3Aissue+gat+is%3Aclosed) and [here](https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=is%3Aissue+generic_associated_types+is%3Aclosed)).
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions