diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-10-27 16:46:56 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-27 16:46:56 +0100 |
| commit | dae8ded9f5821f9dadde15ebca29543a1f20b072 (patch) | |
| tree | 689d86610502f5fcf547ecb91455567c05251868 /src/libstd | |
| parent | 0982060a69e7a3faaa705d0e64bf651872b2f640 (diff) | |
| parent | b93cdbce36b1a42c77b5f3f721d7d64dec80f8f3 (diff) | |
| download | rust-dae8ded9f5821f9dadde15ebca29543a1f20b072.tar.gz rust-dae8ded9f5821f9dadde15ebca29543a1f20b072.zip | |
Rollup merge of #65839 - ecstatic-morse:promo-sanity-fixes, r=eddyb
Clean up `check_consts` now that new promotion pass is implemented `check_consts::resolver` contained a layer of abstraction (`QualifResolver`) to allow the existing, eager style of qualif propagation to work with either a dataflow results cursor or by applying the transfer function directly (if dataflow was not needed e.g. for promotion). However, #63812 uses a different, lazy paradigm for checking promotability, which makes this unnecessary. This PR cleans up `check_consts::validation` to use `FlowSensitiveResolver` directly, instead of through the now obselete `QualifResolver` API. Also, this contains a few commits (the first four) that address some FIXMEs in #63812 regarding code duplication. They could be split out, but I think they will be relatively noncontroversial? Notably, `validation::Mode` is renamed to `ConstKind` and used in `promote_consts` to denote what kind of item we are in. This is best reviewed commit-by-commit and is low priority. r? @eddyb
Diffstat (limited to 'src/libstd')
0 files changed, 0 insertions, 0 deletions
