Alessandro Coglio
Alessandro Coglio
Why was this considered illegal before? (I mean, the latter example.)
Thanks for digging that up. I think that the motivation was ease of compilation to R1CS, but it should be relatively easy to allow that code, which is natural to...
I believe we are still "flying"...
In general, some program analysis or transformation algorithms may take an impractically long time without running out of memory: they may be stuck in a loop that takes long to...
It should be possible to allow this, if we want to. Since `x` is a constant, it is evaluated "away" during flattening. No R1CS variables are allocated for `x`. If...
Yes, `const` inputs must be known and taken into account to ensure that array sizes match up at compile time, since array sizes may depend on `const` inputs. This is...
My reading of the error message ``` = unexpected type, expected: 'array of length 4', received: 'array of length 2' ``` is that it was expecting an array of length...
Right, so I'd call that a type inference error :) I.e. it's inferring the wrong type. I think you are saying that the cause is that we don't know the...
Or we could say it's _calculating_ the wrong type. By 'type inference' I mean the whole type checking/inference pass of the compiler.
This was discussed at today's Leo sync, and it seems that the consensus was for trying and limiting the form of the ``s in ``` [..] ``` to be such...