So can't we just set uninitialized to 0 instead of having this `Int.MaxValue` dance? Yes, the comparison would have to compensate for it instead. Don't know which is worse?