Hugues de Valon

After discussion on Slack and having thought about it a bit more, now agree with making `Mechanism` mutable. Could we make it clear though in the signature of the function...

I see! Then I think we could just change the signature of every function to take a `&mut Mechanism` where before we took a `&Mechanism`. Then we can remove the...

Hello 👋 Thanks for the detailed bug report! I can propose two paths to debug this further: * does multithreading work at all on your RISC-V platform? You could try...

> I would not mind adding the other checks (spell, formatting, clippy, ...) as dependencies as we also want them to succeed. I do not remember what was required before...

Thanks for bringing this up! If there are already forks available I would also prefer using them directly instead of having to maintain the crate ourselves 😅 Do you see...

Then yes I think we can close the PR and plan to switch to an alternative! Hope it was not too much work and thank you for testing it anyway!

We can track [this](https://github.com/rust-lang/rust/issues/124225) which would allow us to remove `paste` and change the code as following when stable: ```diff diff --git a/cryptoki/src/context/general_purpose.rs b/cryptoki/src/context/general_purpose.rs index be7ead9..8c8b3bd 100644 --- a/cryptoki/src/context/general_purpose.rs +++...

> Can you open a PR with the changes? Since we are using stable Rust we can not add those changes until the feature is stabilized sadly :(

Seems like a sensible idea, as long as we can track which kryoptic version we are building and not always build main! I would also be in favour of making...

> moving functions from Pkcs11 to Pkcs11Impl since currently even with Pkcs11Impl::new_unchecked it's actually not possible to call further functions 😬 (since they are on Pkcs11 and it's not possible...