@ieure that seems like a completely different problem I guess?
with goto, you trade the ability to do something that is occasionally useful for the guarantee that code flow is predictable, same as how GC trades malloc for the ability to certain classes of bugs never happen
the seq idiom is just bad naming with no trade-off behind it; it's backed by authority and nothing else