Good point! You're right, it is a little surprising that reduce() adds any overhead at all in this trivial example.

It's interesting that Swift can't seem to fully eliminate that abstraction overhead when runtime checks are enabled -- maybe there's something other than overflow checks that's getting in the way?

The author hints that the abstraction cost does vanish when checks are disabled, but doesn't bother showing any numbers.