-
### Aim
Running tests on the public kernel circuits in the Aztec packages repository.
### Expected Behavior
Tests run.
### Bug
Running `../../noir/noir-repo/target/release/nargo test --package pu…
-
Currently we inject the logs hashes and lengths in TS [here](https://github.com/AztecProtocol/aztec-packages/blob/115f4901d4edc8e4dab1a71bbd0aa672facc6dd1/yarn-project/acir-simulator/src/client/privat…
-
We have a TODO to support operator overloading in the interpreter. We should resolve this and implement this feature.
https://github.com/noir-lang/noir/blob/b3a2c9c86bea8d287fc024090087f3b66bbc31a4…
-
### Aim
I run into an extremely confusing scenario in which the presence of `assert_eq` statements seems to put the program in an inconsistent state in which variables are equal to multiple values …
-
### Problem
Certain algorithms are much more difficult to express without associated types in traits.
### Happy Case
We should support [associated types](https://doc.rust-lang.org/rust-by-example/g…
-
### Aim
I am building a circuit with nargo v0.30.0, but when exporting this to the verifier contract, I can never get the verifier contract to evaluate the proof successfully. However, if I change …
-
### Problem
Running `nargo prove` causes the circuit to be re-compiled on-the-fly, ignoring whether it was already built with `nargo compile`. I'd like to have `nargo prove` use the json file produce…
gnull updated
2 months ago
-
### Problem
https://noir-lang.org/ current lands on the [index.jsx](https://github.com/noir-lang/noir/blob/96fb3e94b3a2f7b586d17ea9445f44267f5d9c6d/docs/src/pages/index.jsx) page with boxes for rea…
-
### Aim
Ran `nargo compile` on:
```rust
fn main() {
let _: Option = Option::none();
}
```
### Expected Behavior
The program to compile without errors
### Bug
```bash
❯ nargo compile
…
-
Original, tout en serif Palatino
![image](https://user-images.githubusercontent.com/5686231/191263399-3ad22000-9772-46bb-97be-fea0ebe8bae5.png)