Results 173 comments of Tom French

I'm also seeing this with the "brillig-constraints-check" SSA pass where if a brillig function returns an array or similar. you'll end up with a warning emitted for every constituent value.

ugh, this is gonna be a pain the the ass.

@guipublic this is now ready for review.

I think that it would be best for us to just wait on this feature until we can have an associated constant applied directly to the integer type impls here...

Hey, I recently implemented a barretenberg-compatible version of pedersen commitments/hashing in https://github.com/noir-lang/noir/pull/4871 working off of the existing implementation in barustenberg as a base. I had to make the `hash_to_curve` function...

The only remaining task is #6934 which is already part of the 1.0 milestone so we can close this.

A couple of examples where the LSP doesn't realise that a struct has been constructed: Usage of `std::mem::zeroed()` is not considered to construct the `Foo` struct. ```noir struct Foo {}...

This would be implemented by writing a new brillig directive similar to those in https://github.com/noir-lang/noir/blob/master/compiler/noirc_evaluator/src/brillig/brillig_gen/brillig_directive.rs. We could then have the acir-gen code emit a call to this rather than a...

Closed by https://github.com/AztecProtocol/aztec-packages/pull/9970

> Was the circuit size changes CI item removed? I don't see it listed. It was removed temporarily for some reason I can't quite remember but it's back now.