Dylan DPC bbd3a10663

Rollup merge of #103774 - compiler-errors:dyn-trait-in-type-name, r=eholk ...

Format `dyn Trait` better in `type_name` intrinsic

Noticed this in #103764 (though not related to that PR at all!)

```rust
trait Foo {
    type Bar;
}

fn main() {
    println!(
        "`dyn Fn(i32, i32) -> i32` => `{}`",
        std::any::type_name::<dyn Fn(i32, i32) -> i32>()
    );
    println!(
        "`dyn Foo<Bar = i32> + Send + Sync` => `{}`",
        std::any::type_name::<dyn Foo<Bar = i32> + Send + Sync>()
    );
}
```

```
`dyn Fn(i32, i32) -> i32` => `dyn core::ops::function::Fn<(i32, i32)>+Output = i32`
`dyn Foo<Bar = i32> + Send + Sync` => `dyn playground::Foo+Bar = i32+core::marker::Sync+core::marker::Send`
```

Just reuse `pretty_print_dyn_existential` which already makes an attempt to make its output stable.

2022-11-02 22:32:03 +05:30

..

benches

add a benchmark for slice_iter.copied().array_chunks()

2022-10-17 23:40:21 +02:00

primitive_docs

…

src

Rollup merge of #103084 - inquisitivecrystal:control-flow, r=scottmcm

2022-11-01 20:00:37 -04:00

tests

Format dyn Trait better in type_name intrinsic

2022-11-01 20:41:47 +00:00

Cargo.toml

Avoid use of rand::thread_rng in stdlib benchmarks

2022-05-02 00:08:21 -07:00