Exhaustive and rationalized list of builtins in uplc builder.

[waalge]

What is your idea? Provide a use case.

More explicitly:
Make the methods

aiken/crates/uplc/src/builder.rs

Line 153 in 67986d9

pub fn add_integer() -> Self {

Stay in lock step with

aiken/crates/uplc/src/builtins.rs

Line 15 in 67986d9

AddInteger = 0,

With PascalCase -> snake_case

Why is it a good idea?

It'll be easier to maintain and for others to use if it reflects the builtins as they are elsewhere.
Don't have to remember Subtract is sub and that MultiplyInteger doesnt have a builder.
And if it did it's clear where in the list it ought to appear

What is the current alternative and why is it not good enough?

Keep things ad hoc and inexhaustive so people are put off trying to use them.

[waalge]

• maybe with the additional mapping of ByteString to bytearray

aiken/crates/uplc/src/builder.rs

Line 137 in 67986d9

pub fn equals_bytestring() -> Self {

Although can't see that this is actually used

[MicroProofs]

hmm let's discuss more but I think ordering everything is fine.

[waalge]

Happy to move to a discussion

The later builtins are more involved with addtional force used.

And then there's the additional cases of delay_x

I don't know what's best for these, but I think there's enough builtins that this would be better somewhat rationalized

[waalge]

All the other bytestrings are bytearrays here
Example:

aiken/crates/uplc/src/builder.rs

Line 141 in 67986d9

pub fn less_than_bytearray() -> Self {

---

An asside and a bit too late in the day but: the use of ByteArray over ByteString together with aiken using bytearray rather than byte_array grates mildly.