[perf] Decouple directly accessing a HIR owner from ast lowering by oli-obk · Pull Request #138705 · rust-lang/rust (original) (raw)
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
Status: Awaiting review from the assignee but also interested parties.
Relevant to the compiler team, which will review and decide on the PR/issue.
labels
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf] Decouple directly accessing a HIR owner from ast lowering
r? @ghost
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf] Decouple directly accessing a HIR owner from ast lowering
r? @ghost
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf] Decouple directly accessing a HIR owner from ast lowering
r? @ghost
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf] Decouple directly accessing a HIR owner from ast lowering
r? @ghost
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf experiment] Split the resolver tables into per-owner tables
r? @ghost
just doing some experiments to see if splitting hir_crate is feasible by checking if splitting the resolver's output into per-owner queries is feasible (rust-lang#95004)
Basically necessary for rust-lang#138705 as that can't be landed perf-wise while the hir_crate query is still a thing
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf experiment] Split the resolver tables into per-owner tables
r? @ghost
just doing some experiments to see if splitting hir_crate is feasible by checking if splitting the resolver's output into per-owner queries is feasible (rust-lang#95004)
Basically necessary for rust-lang#138705 as that can't be landed perf-wise while the hir_crate query is still a thing
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf experiment] Split the resolver tables into per-owner tables
r? @ghost
just doing some experiments to see if splitting hir_crate is feasible by checking if splitting the resolver's output into per-owner queries is feasible (rust-lang#95004)
Basically necessary for rust-lang#138705 as that can't be landed perf-wise while the hir_crate query is still a thing
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf experiment] Split the resolver tables into per-owner tables
r? @ghost
just doing some experiments to see if splitting hir_crate is feasible by checking if splitting the resolver's output into per-owner queries is feasible (rust-lang#95004)
Basically necessary for rust-lang#138705 as that can't be landed perf-wise while the hir_crate query is still a thing
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf experiment] Split the resolver tables into per-owner tables
r? @ghost
just doing some experiments to see if splitting hir_crate is feasible by checking if splitting the resolver's output into per-owner queries is feasible (rust-lang#95004)
Basically necessary for rust-lang#138705 as that can't be landed perf-wise while the hir_crate query is still a thing
bors added a commit to rust-lang-ci/rust that referenced this pull request
[perf experiment] Split the resolver tables into per-owner tables
r? @ghost
just doing some experiments to see if splitting hir_crate is feasible by checking if splitting the resolver's output into per-owner queries is feasible (rust-lang#95004)
Basically necessary for rust-lang#138705 as that can't be landed perf-wise while the hir_crate query is still a thing