about summary refs log tree commit diff
path: root/compiler/rustc_codegen_cranelift/example/alloc_example.rs
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2023-02-23 06:18:07 +0100
committerGitHub <noreply@github.com>2023-02-23 06:18:07 +0100
commitd6077f895aa805394c0371365d4bf0f1c368dc02 (patch)
tree86529239bd46414d9cdc56b018dea3818e1060d2 /compiler/rustc_codegen_cranelift/example/alloc_example.rs
parent2011ced333fb800d7101568a3f1588572b77ba19 (diff)
parent729cd55688f0c7e39087b934f1d733813bf0a71a (diff)
downloadrust-d6077f895aa805394c0371365d4bf0f1c368dc02.tar.gz
rust-d6077f895aa805394c0371365d4bf0f1c368dc02.zip
Rollup merge of #108350 - compiler-errors:assoc-type-bound-dogfooding, r=oli-obk
Use associated type bounds in some places in the compiler

Use associated type bounds for some nested `impl Trait<Assoc = impl Trait2>` cases. I'm generally keen to introduce new lang features that are more mature into the compiler, but maybe let's see what others think?

Side-note: I was surprised that the only use-cases of nested impl trait in the compiler are just iterator related?!
Diffstat (limited to 'compiler/rustc_codegen_cranelift/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions