diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2020-03-21 08:51:18 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-21 08:51:18 +0100 |
| commit | a6d0c35e869f88ba04b17a9befa2024721a579b4 (patch) | |
| tree | 5451b60f7fedea60d94333306c79bd16a9a68526 /src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs | |
| parent | bbd1ca3b69efc500eaadc11146506815c98ed93e (diff) | |
| parent | 63811bc38f5fcb8bc83e2dd8719ce5444bb277f0 (diff) | |
| download | rust-a6d0c35e869f88ba04b17a9befa2024721a579b4.tar.gz rust-a6d0c35e869f88ba04b17a9befa2024721a579b4.zip | |
Rollup merge of #70089 - eddyb:closure-sig-infer, r=nikomatsakis
rustc_infer: remove InferCtxt::closure_sig as the FnSig is always shallowly known. That is, `ClosureSubsts` is always created (in `rustc_typeck::check::closure`) with a `FnSig`, as the number of inputs is known, even if they might all have inference types. The only useful thing `InferCtxt::closure_sig` was doing is resolving an inference variable used just to get the `ty::FnPtr` containing that `FnSig` into `ClosureSubsts`. The ideal way to solve this would be to add a constructor for `ClosureSubsts`, that combines the parent `Substs`, the closure kind, the signature, and capture types together, but for now I've went with resolving the inference types just after unifying them with the real types. r? @nikomatsakis
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions
