about summary refs log tree commit diff
path: root/src/test/rustdoc-ui/coverage/basic.rs
diff options
context:
space:
mode:
authorDylan DPC <dylan.dpc@gmail.com>2020-04-21 00:30:57 +0200
committerGitHub <noreply@github.com>2020-04-21 00:30:57 +0200
commit42b533d7ba92dbc6ab3b6de59bae44f629b93d66 (patch)
treea7033bb1a03396644459b745b116166d5fad7945 /src/test/rustdoc-ui/coverage/basic.rs
parente3a514c44a7a896b210dcc59635452229703b9e6 (diff)
parent3c455fe8e1712af5996232053cd6ea3ea743a487 (diff)
downloadrust-42b533d7ba92dbc6ab3b6de59bae44f629b93d66.tar.gz
rust-42b533d7ba92dbc6ab3b6de59bae44f629b93d66.zip
Rollup merge of #71285 - ljedrz:mir_inline_span_for_optimized_mir, r=ecstatic-morse
MIR: use HirId instead of NodeId to avoid cycles while inlining

I wanted to see if I could limit the number of uses of `NodeId` when `HirId` is available and I saw that some of the MIR `Inliner` code could use `Span` instead of `NodeId`, not unlike in https://github.com/rust-lang/rust/pull/71197.

~If I'm understanding the reason for not calling `optimized_mir` in incremental builds here correctly, this change could also allow us to do so.~

This change could affect performance, so if this approach makes sense, a perf run is probably a good idea.
Diffstat (limited to 'src/test/rustdoc-ui/coverage/basic.rs')
0 files changed, 0 insertions, 0 deletions