-
### Description
Hyphenation rules defined by document language aren't taken into account when exporting to PDF LaTeX. In my case, adding `lang: fr` in the YAML front-matter or in the defaults file do…
-
# Problem
See the TODO added here:
https://github.com/noir-lang/noir/pull/546#discussion_r1043743460
# Solution
# Alternatives considered
(Describe any alternative solutions you have …
-
# Description
## Aim
Build Noir from sources.
## Expected behavior
Successful build.
## Bug
```
(base) oberstet@intel-nuci7:~/scm/3rdparty/noir/crates/nargo$ cargo install --locked …
-
# Description
`nargo prove` returns `0` exit status (success) when it fails
## Expected behavior
Should return non-zero exit status on failure
## Bug
```
$ nargo prove p
ACIR gates ge…
-
The following circuit will ICE the compiler with a witness assignment not found error. This only happens if the gates are out of order, since we have the compiler guaranteeing that variables are both …
-
# Problem
Currently split is not a descriptive name for what the directive is doing.
# Solution
Rename Split to Binary decomposition or a more descriptive name.
# Alternatives considered
…
-
# Description
I cannot build `nargo` on the Ubuntu Mainframe when the reference `aztec_backend` reference inside `nargo`'s `Cargo.toml` file is changed to the most recent commit for the [aztec_back…
-
# Description
## Aim
```
fn bar(a: [u8;2*2]) {
constrain a[0]>1;
}
bar([1,2,3,4]);
```
## Expected behavior
No error
## Bug
`error: Expected a ] but found *`
# To reprodu…
-
# Description
Following instructions on https://noir-lang.github.io/book/getting_started/nargo/installation.html with [Option 1: WASM Executable Backend](https://noir-lang.github.io/book/getting_st…
-
# Description
## Aim
The compiler appears to support `for` loop returns as mapped expressions, even though this is unimplemented in the prover. The user should be informed at compile time that t…