d0cd
d0cd
## 💥 Proposal The errcov utility helped us determine which errors were covered in our test suite. Helpful for getting coverage metrics.
## 💥 Proposal The compiler's interface can be simplified to `compile` and `compile_with_file`. The interface for constructing the object can simplified so that it is not needed to instantiate the...
## 🚀 Feature The current test framework defaults to `TestnetV0`. While there aren't many differences between our networks, parameterizing the framework would allow us to test network specific properties like...
## 🚀 Feature `snarkVM` has a limit of `16` inputs and `16` outputs per transition/function. Leo can overcome these limits by repackaging all non-record inputs and outputs into a "canonical"...
## 🚀 Feature A CLI utility to verify: - transactions produced by snarkVM. - raw Varuna proofs produced by snarkVM. For either option, the utility will need to take in...
The Leo CLI relies on the `.env` file to set some parameters. It would also be nice if the CLI chose some defaults for network and endpoint (if not provided)...
^ The default one should be stored in the home directory. Actually, a more interesting idea would be do have "profiles" in the CLI. Counterpoint would be that it's adding...
The Leo compiler should be able to correctly support hashing of arbitrary data types, but catching the correct size in the case of the Pedersen variants.
^
The Updater struct is superfluous, and its associated functions and consts should just be in the top level of the updater module.