about summary refs log tree commit diff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2022-04-13 07:50:56 +0000
committerbors <bors@rust-lang.org>2022-04-13 07:50:56 +0000
commit27634b03ea78262816ee8b48f8e3538ec32b965b (patch)
treea12c9edb068825ac97d95c4e8e1b015c6302772a /tests/rustdoc-js-std/parser-errors.js
parent62d912e24dc1ec3816dfcddba96c792b660edc9b (diff)
parent2f780758099bd649e8b9434449ec5e303e31e1aa (diff)
downloadrust-27634b03ea78262816ee8b48f8e3538ec32b965b.tar.gz
rust-27634b03ea78262816ee8b48f8e3538ec32b965b.zip
Auto merge of #94255 - b-naber:use-mir-constant-in-thir, r=oli-obk
Use mir constant in thir instead of ty::Const

This is blocked on https://github.com/rust-lang/rust/pull/94059 (does include its changes, the first two commits in this PR correspond to those changes) and https://github.com/rust-lang/rust/pull/93800 being reinstated (which had to be reverted). Mainly opening since `@lcnr` offered to give some feedback and maybe also for a perf-run (if necessary).

This currently contains a lot of duplication since some of the logic of `ty::Const` had to be copied to `mir::ConstantKind`, but with the introduction of valtrees a lot of that functionality will disappear from `ty::Const`.

Only the last commit contains changes that need to be reviewed here. Did leave some `FIXME` comments regarding future implementation decisions and some things that might be incorrectly implemented.

r? `@oli-obk`
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions