diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-09-28 05:37:47 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-09-28 05:37:47 +0200 |
| commit | 00cba5b092beedb75db307aaa8fedeae3a9d589a (patch) | |
| tree | b7018a29a4d9387ca2db11315d677b306e9a6225 /src/test/debuginfo/enum-thinlto.rs | |
| parent | 5b6a5801fbe90c029a170555c1ca49b676b243a7 (diff) | |
| parent | c3368bdfa498f0c8fb2267dfb0cb804df8ec6dbb (diff) | |
| download | rust-00cba5b092beedb75db307aaa8fedeae3a9d589a.tar.gz rust-00cba5b092beedb75db307aaa8fedeae3a9d589a.zip | |
Rollup merge of #64809 - davidtwco:issue-64768-target-feature-const, r=varkor
hir: Disallow `target_feature` on constants Fixes #64768. This PR fixes an ICE when `#[target_feature]` is applied to constants by disallowing this with the same error as when `#[target_feature]` is applied to other places it shouldn't be. I couldn't see anything in the [RFC](https://github.com/rust-lang/rfcs/blob/master/text/2045-target-feature.md) that suggested that `#[target_feature]` should be applicable to constants or any tests that suggested it should, though I might have missed something - if this is desirable in future, it remains possible to remove this error (but for the time being, I think this error is better than an ICE). I also added some extra cases to the test for other places where `#[target_feature]` should not be permitted. cc @gnzlbg
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions