Sergey "Shnatsel" Davidoff

Related: invitations never expire (#2869)

A one use case such privacy prevents is detailed listing of all owners by [`cargo supply-chain`](https://github.com/rust-secure-code/cargo-supply-chain), but this is probably a reasonable trade-off.

@saethlin Address Sanitizer already detects both out-of-bounds indexing and improper use of `copy_nonoverlapping`, and it is already enabled by default, so I don't think this provides much benefit as a...

Superseded by #339

We could add debug level 2 to the defaults so that full debug info is available by default. Then there's no need to drop down to `--dev`.

It is a binary crate, not used as a dependency by any other crates, so if we file an advisory if will not be surfaced through most tools. Although perhaps...

Oh, the backbuffer is still needed. I'm talking about this allocation: https://github.com/fschutt/fastblur/blob/3abecde49b3abdd73fe950e01eab9bf7b6e16dc9/src/blur.rs#L32

`.collect()` would still allocate, but you can avoid collecting by returning the iterator directly. This is available since Rust 1.26: https://doc.rust-lang.org/edition-guide/rust-2018/trait-system/impl-trait-for-returning-complex-types-with-ease.html The trait you want to return in this case...

Well, for `Impl Iterator` instead of allocations is actually slightly slower than allocating a `Vec` (well, [my attempt](https://github.com/Shnatsel/fastblur/tree/iterator-box) is), so I guess arrays are the way to go.

Riiiight, of course the proprietary platform I don't have access to will fail :facepalm: Time to take up that offer from a Mac renting company and put an ad for...