d0cd

The current system is not future proof and is hard to incorporate changes. A full rewrite with type inference is probably needed.

[Feature] `CheatCode::set_signer`

1

## 🚀 Feature A cheat code to set the signer via private key could be useful. For example, `CheatCode::set_signer()`. An open question is how should the private key be passed...

[Feature] Use lock files to determine when depdencies change when switching networks.

1

^

## 📚 Documentation We propose the following coding conventions for the Leo language: - `async function`s should be suffixed with an underscore `_`

## 🚀 Feature With writable composite data types, we should consider the implications of re-introducing the `mut` keyword. ### For - Allows developers to explicitly clarify intention ### Against -...

## 🚀 Feature The AVM provides users with `mappings` but they can be somewhat unwieldy to use. Specifically users may want: - a global singleton (requires the use of one...

[Proposal] Coding Standards

2

## 💥 Proposal We propose the following coding standards for Leo: - If code is unreachable for all invocations, use the `unreachable!` macro. - Do not use unwraps, use `expect`...

## 💥 Proposal snarkVM provides a `Package` which has a basic set of features, but is opinionated in how these objects can be constructed. Leo allows for richer project structures...

The manifest should specify the Leo version. This is good hygiene in the case of breaking language features. In addition, the Leo CLI should be able to download and manage...

## 💥 Proposal The leo benchmarking framework was removed as it was not actively in use. This framework analyzed the performance of each compiler pass. Revive if we want metrics...