CIP-0138 array

[Unisay]

Closes ##6731

[ana-pantilie]

This doesn't implement the builtin functions, right? It just defines them and the compiler recognizes them as builtins, but the evaluator doesn't yet know how to evaluate them. I assume that will be done in a separate commit/PR.

[zliu41]

New parameters must be appended, not inserted in the middle.

And these names don't seem accurate - e.g., ListToArray is linear, so there needs to be an intercept and a slope. If they aren't accurate, then I'm not sure what the point is adding them at all. @kwxm What do you think?

[zliu41]

Also these need to be added to V1 and V2 as well.

[Unisay]

New parameters must be appended, not inserted in the middle.

👍🏼 I wrote a golden test which will fail if this condition is violated

And these names don't seem accurate - e.g., ListToArray is linear, so there needs to be an intercept and a slope. If they aren't accurate, then I'm not sure what the point is adding them at all.

The point is to make build green. Some parameters have to be added, otherwise CI tests fail.

[zliu41]

I wrote a golden test which will fail if this condition is violated

How do we update the golden file when new parameters are added?

The point is to make build green. Some parameters have to be added, otherwise CI tests fail.

I'll let @kwxm check whether this is the right thing to do.

[Unisay]

How do we update the golden file when new parameters are added?

cabal test plutus-ledger-api-test fails if new parameter names were inserted in the middle, not appended.
cabal test plutus-ledger-api-test --test-options --accept updates the golden file.