Tony Arcieri
Tony Arcieri
Oh wow, definitely an important detail about `core::hint::black_box`! An ASM optimization barrier seems good then, although let me run this implementation by a few people. It would definitely still be...
Hmm, when did that warning get added? It doesn't appear on the current stable docs. Is it new? https://doc.rust-lang.org/stable/std/hint/fn.black_box.html
This is the optimization barrier @chandlerc recommended (C++ version, similar idea): https://compiler-explorer.com/z/bh9WzvTPq
> Maybe I looked up the wrong docs, my url says "beta". Maybe they removed that later. To me that implies those docs were recently added. I guess we'll see...
A PR to add FreeBSD support would be accepted, although I'm not sure what a good CI story for it is
Re: ARM, we only currently support AArch64, where the `neon` target feature is always enabled
MCUs are also a bit of a different use case from our other ARM targets, where CPU feature detection is a privileged operation and we have to ask the OS...
We could potentially add something like this, but I'll note the API surface is already pretty complicated. I'm not sure it makes sense to add these to `AeadInPlace`: they're not...
Pretty much all of our AEADs impl `AeadCore`+`AeadInPlace`, and there's already a blanket impl of `Aead` for `AeadCore`. The `*Mut` traits are pretty much there to support hardware accelerators and...
To back up, what you want isn't an in-place API, but one which has an immutable reference to the source and a mutable reference to the destination buffer. So, it...