Tom French

Swap out `ln` and `exp` for Solmate versions

3

# Description This swaps out the exp and ln implementations for the solmate version. ## Type of change - [ ] Bug fix - [ ] New feature - [...

# Description ## Problem\* Closes #4562 ## Summary\* This PR adds a test for verifying 2 proofs inside of another proof to the integration tests. ## Additional Context ## Documentation\*...

feat: catch imports of private definitions in resolution

6

# Description ## Problem\* Resolves ## Summary\* Currently Noir only defines import visibility for functions, while everything else is implicitly public. This PR is an experiment on adding proper import...

feat: add `unsafe` blocks for calling unconstrained code from constrained functions

6

# Description ## Problem\* Resolves ## Summary\* This is an experimental PR to play around with unsafe blocks as a method to make it clearer when unconstrained values are entering...

This is currently all TODO'd https://github.com/noir-lang/noir/blob/b3fd24d77e141c3a6562b6bcfc62d2ecb572e191/acvm-repo/brillig_vm/src/black_box.rs#L181-L186

feat: add optimization pass to remove witness equality constraints

1

# Description ## Problem\* Resolves ## Summary\* This PR adds a new optimisation pass which removes constraints which just constrain one witness to be equal to another and instead replaces...

Epic: Add visibility system to hide implementation details internal to modules

1

### Problem Currently all types/values defined in Noir are public, this causes an issue where libraries cannot provide a restricted interface as users can reach in an import internal implementation...

`Instruction::has_side_effects` and `Instrinsic::has_side_effects` are not accurate.

4

There's a number of `Instruction`s and `Intrinsic`s which use the `side_effects_enabled_var` variables in ACIR gen. This has a couple of knock-on-effects: - We perform dead instruction elimination were we (maybe?)...

We removed the behaviour where tests would be printed to the console as they were started and completed as this would have broken when tests were made to run in...

Restrict usage of unconstrained functions to within `unsafe` blocks

7

# Problem It's currently not obvious when we're calling an unconstrained function (and introducing unconstrained values into the circuit). It's then quite difficult to rule out that any under-constrained bugs...