The new version seems to fix that since your comment was written, but it will stil panics if less than 2 samples are provided, unless the crate it wraps panics at an earlier point.

let peak = buf
            .iter()
            .copied()
            .enumerate()
            .take(self.sample_count / 2)
            .max_by_key(|(_, s)| (s.abs() * 1000.0) as u32)
            .expect("to have at least 1 sample");

Um actually🤓, that’s not pizza specific.

Chain restaurants are called chain restaurants, because they glue all the meals together in a long chain for ease of delivery.

They are wearing the clean room masks below their noses. I wouldn’t trust them with regular computers.

E = mc^2 and E = mc^2 + AI
mc^2 = mc^2 + AI
0 = AI

Therefore AI is worthless.

I looked at the diff, it’s around 100 lines of new code and a few hundred lines of comments and tests.
I couldn’t have written it, but there are many smarter people that fixed it after they learned of the problem.

What also made it easier to fix is that they (sensibly) chose to error on certain strings that can’t be escaped safely.

Keyword reserving is always exciting.
In this case it’s gen, which allows iterators build on the state machines currently powering async.

Here is a contrived use case from me.
It’s not as groundbreaking as async but it’s a convenience. And hey, you could write futures without the async/await keywords, but it’s easier with them