Some consumers may want to provide their own Kecak implementations instead of using the ones provided by us. Such implementations may be using Keccak implementations using dynamic memory allocations, e.g., the Keccak from OpenSSL does that.
In that case, we need to explicitly free the state once it is no longer needed.
This PR adds corresponding functions called _ctx_release() and calls them in the appropriate places.
Since all of our Keccak implementations use a statically allocated state, the xxx_ctx_release() is implemented as a no-op here.
Some consumers may want to provide their own Kecak implementations instead of using the ones provided by us. Such implementations may be using Keccak implementations using dynamic memory allocations, e.g., the Keccak from OpenSSL does that. In that case, we need to explicitly free the state once it is no longer needed.
This PR adds corresponding functions called _ctx_release() and calls them in the appropriate places. Since all of our Keccak implementations use a statically allocated state, the xxx_ctx_release() is implemented as a no-op here.
Naming of functions follows PQClean and liboqs.