[swift-evolution] Epic: Typesafe calculations
greg at omnigroup.com
Sun Dec 27 16:33:48 CST 2015
> On Dec 27, 2015, at 2:56 AM, Tino Heth <2th at gmx.de> wrote:
>> There’s some unfortunate extra boilerplate here, which could be better handled with newtype support in the language, but when compiled with optimizations the resulting code is nearly identical to using plain Ints.
> Cool — have you checked the generated assembler for this conclusion? But I guess there is some knowledge on how to build an optimizing compiler in the core team ;-), so I'd expect little to no penalty (I guess the memory footprint of plain Ints is still better).
Yes, I have, and actually, the memory footprint is no different! These are value-types that are exactly word-sized, and so get passed around in registers and stored inline in larger structs.
More information about the swift-evolution