That's slightly different, though. The first is "when this is true, earlier in the function, queue up running something at the end of the function." This is "at

That's slightly different, though. The first is "when this is true, earlier in the function, queue up running something at the end of the function." This is "at the end of the function, if this is true, do something." They _should_ be identical, unless shouldDoSideEffect changes. Yes, mutability is bad. One shouldn't change that. But avoiding "you're holding it wrong" footguns was the original goal, right? Don't get me wrong, having both would be nice. Maybe something like `after` for function scope and `defer` for block scope. But that starts to erode the "simplicity" of Go, I guess.