Franziskus Kiefer

I can see why you would need that for performance improvements, but there should be a comment saying that this is equivalent to the identity function semantics-wise because the formal...

Add SPARKLE spec https://csrc.nist.gov/CSRC/media/Projects/lightweight-cryptography/documents/round-2/spec-doc-rnd2/sparkle-spec-round2.pdf

Implement a spec for `BIP32-Ristretto` see also https://github.com/iqlusioninc/crates/issues/738

Fail on/remove library functions that are not in hacspec

3

The hacspec-lib contains functions that are nor in hacspec (marked with the `not_hacspec` attribute). These functions are not allowed in hacspec but can be used right now. There are two...

There are some primitives in the hacspec python version we could re-implement here - [ ] [XMSS](https://github.com/HACS-workshop/hacspec/blob/master/specs/xmss.py) - [ ] [VRF](https://github.com/HACS-workshop/hacspec/blob/master/specs/vrf.py) - [ ] [RSA-PSS](https://github.com/HACS-workshop/hacspec/blob/master/specs/rsapss.py) - [ ] [Kyber](https://github.com/HACS-workshop/hacspec/blob/master/specs/kyber.py) -...

Allow let-bindings without initialization

8

It is currently not allowed to use `let x = if ...` bindings. But it is also not allowed to use let declarations `let x: u8;`. This leads to Rust...

Allow integer downcasting

6

It is currently impossible to downcast integers, e.g. `usize` to `u8`, which is needed sometimes. It would probably be best to allow `TryFrom` conversions that have to be unwrapped, e.g....

array! u8/U8 and bytes! should use the same implementation

2

Currently `array!(State, 8, U8, type_for_indexes: StateIdx)` is a different implementation than `bytes!(State, 8)`. That's confusing and unnecessary.

Don't allow old style arrays

3

Remove support for arrays without index type.