diff options
| author | kennytm <kennytm@gmail.com> | 2019-01-05 23:57:06 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-01-05 23:57:06 +0800 |
| commit | d9885c41de48145c6177ed4dd7d24a10e350f1d1 (patch) | |
| tree | 6a91654cfc5fcfb437a6ac147a391caf2d2ca5a1 /src/rustllvm/RustWrapper.cpp | |
| parent | 06c07f93c023ac619bd09fb9d76625705eadfeb7 (diff) | |
| parent | 480d0f3a317f8bd4404bfe4df220300372a110c8 (diff) | |
| download | rust-d9885c41de48145c6177ed4dd7d24a10e350f1d1.tar.gz rust-d9885c41de48145c6177ed4dd7d24a10e350f1d1.zip | |
Rollup merge of #57343 - Xanewok:querify-access-levels, r=nikomatsakis
Calculate privacy access only via query Initially converted to query in https://github.com/rust-lang/rust/commit/a9f6babcda1479f4e5566d1aadbf9a0d99aa3182 and then changed to respect dependencies https://github.com/rust-lang/rust/commit/8281e883dd12260f00ce650aa8824507d9c447af. I did this as an effort to prune `CrateAnalysis` from librustc_save_analysis, with the only thing remaining being the glob map (`name` is unused, existing `crate_name` is exposed in the compiler passes, instead). Since calculating the glob map is opt-in, it'd be great if we could calculate that on-demand. However, it seems that it'd require converting resolution to queries, which I'm not sure how to do yet. In an effort to get rid of `CrateAnalysis` altogether, could we try unconditionally calculating the glob_map in the resolver, thus completely removing `CrateAnalysis` struct, and doing a perf run? r? @nikomatsakis cc @petrochenkov do you have any idea how/if at all could we querify the resolver? I've stumbled upon a comment that's ~3? years old at the moment, so I'm guessing things might have changed and it actually may be feasible now. https://github.com/rust-lang/rust/blob/fe0c10019d7ee96909cc42cc265ef999a6b5dd70/src/librustc_driver/driver.rs#L589-L593
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
