since values are already immutable, making copies of them doesn't make sense,
only creating indirections that must then be tracked by the optimizer

Blocks with more than one parent were being multiple times

By having most control flow constructs of the language use the negated version of their condition instead of the condition itself,
we can prevent (most of the time) the ugly code generation that caused two parts of the same construct (e.g. a for loop) to be distant from each other on the generated code.
While that didn't  have any impact on performance, it still made the generated code harder to read and reason about.

Since the end instruction does the same thing as a jump 0 always, the end-if represents its conditional counterpart, allowing us to use a single instruction
in the generated code to do something previously done by two

For some reason I suddenly started having cyclical dependency issues in which EJumpKind would be undefined
so I decided to just remove the file since it was no longer used anyways