Skip to content

proposal for destructive comparison opcode #5

@zack-bitcoin

Description

@zack-bitcoin

we have an opcode to check if things are equal, and it leaves those things on the stack.
This is a good optimization for using ram while processing the smart contract, but it means we are using 4 opcodes every time we check equivalence, which is something we do in practically every function.

If we also had an equivalence operator that destroyed the things after comparing them, it would save 3 bytes per comparison in a program.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions