Make `expand` and `encrypt` public.

[qm3ster]

Make `expand` and `encrypt` public.

[newpavlov]

Unfortunately this will not be easy. In the case of aesni exapnsion, encryption and decryption rounds are inlined for performance reasons, and in the case of aes-soft code is somewhat convoluted. I think your best shot will be to use aesni as a reference and write your target function directly. If you'll have any questions I will be glad to answer them!

[qm3ster]

IIRC, having it marked inline but also exporting it would still inline and fully optimize the version used internally.
Furthermore, it would export not bindings to a "compiled" version but essentially export the AST as part of the metadata, meaning it would even get inlined into consumer crates, giving great performance to unorthodox uses.
Am I totally wrong?

[newpavlov]

One round of encryption is just one _mm_aesenc_si128 call, so I don't think it makes sense to expose wrapper around one intrinsic. As for key expansion, currently intrinsic requires const argument, so I am using macros because of it. (see this topic) I don't see how it can be cleanly exposed in public API. (especially in the case of AES-192 which has more convoluted key schedule)