You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the first case I don't see why it would matter to use OP_NUMEQUAL rather than OP_EQUAL (they are functionally the same in this case so what is the benefit of making the breaking change?)
the second case would indeed save one opcode 👍 I quickly confirmed the compiler behavior on the playground
Making breaking changes to the compiler is only something we want to do very infrequently
bool b, bool a;
a == b
should compile to OP_NUMEQUAL (rather than OP_EQUAL)a != b
should compile to OP_NUMNOTEQUAL (rather than OP_EQUAL OP_NOT)The text was updated successfully, but these errors were encountered: