[swift-evolution] Epic: Typesafe calculations
tim.thawkins at gmail.com
Tue Dec 29 08:28:21 CST 2015
This just popped up on HN and may be relevant to this discussion.
On Tue, Dec 29, 2015, 16:11 Howard Lovatt via swift-evolution <
swift-evolution at swift.org> wrote:
> +1 for the ability to unit check expressions. It is harder to do than it
> sounds because there are many equivalent units, for example force N = mass
> kg * acceleration m/s^2. Therefore N, kg m/s^2, m/s^2 kg, etc. are all
> Sent from my iPad
> > On 28 Dec 2015, at 9:33 AM, Greg Titus via swift-evolution <
> swift-evolution at swift.org> wrote:
> >> 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.
> > - Greg
> > _______________________________________________
> > swift-evolution mailing list
> > swift-evolution at swift.org
> > https://lists.swift.org/mailman/listinfo/swift-evolution
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution