diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-11-24 08:42:35 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-11-24 08:42:35 +0100 |
| commit | 6938717ca5fe8035d4aea3cf89664afdd6b137b1 (patch) | |
| tree | fdf96bb1d8ee712a064b954ab5a715fe849a5a30 /compiler/rustc_codegen_llvm/src | |
| parent | c08c57e856e0536accad812d43f458004c439613 (diff) | |
| parent | 024bb8c7fb8b31e36e559a566bcaf4e7a85fe36b (diff) | |
| download | rust-6938717ca5fe8035d4aea3cf89664afdd6b137b1.tar.gz rust-6938717ca5fe8035d4aea3cf89664afdd6b137b1.zip | |
Rollup merge of #104753 - compiler-errors:drop-tracking-var-ice, r=oli-obk
Pass `InferCtxt` to `DropRangeVisitor` so we can resolve vars The types that we encounter in the `TypeckResults` that we pass to the `DropRangeVisitor` are not yet fully resolved, since that only happens in writeback after type checking is complete. Instead, pass down the whole `InferCtxt` so that we can resolve any inference vars that have been constrained since they were written into the results. This is similar to how the `MemCategorizationContext` in the `ExprUseVisitor` also needs to pass down both typeck results _and_ the inference context. Fixes an ICE mentioned in this comment: https://github.com/rust-lang/rust/issues/104382#issuecomment-1324410781
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
