Artyom Pavlov

We can not do anything on our side apart from releasing new crate versions which use `hybrid-array`. Also, see the `generic-array` issue: https://github.com/fizyk20/generic-array/issues/158

There are some minor blockers which I would like to resolve before cutting new releases. Hopefully, it will be done before the year's end. I believe that the best near-term...

We plan to release new versions before the year's end. MSRV will be equal to 1.85. The easiest solution in the near term is to pin `generic-array` to v0.14.7 either...

@oconnor663 Good idea! I should've considered it sooner.

crypto-common v0.1.7 with pinned generic-array is released! Downstream users should be able to remove the pinning in their crates after `cargo update`.

>I'm attaching the flamegraph generated for version 0.9.0-rc.2. The flamegraph shows that `encrypt_par` did not get inlined. This causes generated CTR and keystream blocks to be spilled to stack instead...

Sounds good to me, but are you sure that we don't want the examples to be part of crates README?

Yes, this is why I am asking whether you are sure that we do not want the examples to be part of README. It's one of the first places users...

A potential alternative could be to add extended docs and examples to the `aead` crate (e.g. to a separate `cookbook`/`tutorial` module) or to the book and link them from the...

We do not have links to a text equivalent to the [hashes README](https://github.com/RustCrypto/hashes/blob/master/README.md#examples), so it's not surprising that people find the current [`aead` docs](https://docs.rs/aead/) a bad starting point. I think...