[swift-evolution] Epic: Typesafe calculations

[davesweeris at mac.com]

> On Jan 8, 2016, at 02:42, Tino Heth <2th at gmx.de> wrote:
>> Those are both on the todo list, though, aren’t they?
> I can't prove you wrong, but do you have evidence?
> (that would be great - non-type template arguments are definitely on my to-propose list ;-)

Depends on what you mean by “evidence”. I’ve been trying to remember what I was thinking of when I wrote that, and I *think* it was the word “when” (as opposed to “if”) in one of Dave Abrahams’s earlier posts in this thread:


> On Dec 31, 2015, at 09:25, Dave Abrahams via swift-evolution <swift-evolution at swift.org> wrote:
>> If Swift would support non-type generic parameters, then I would like to have Boost.Unit library (http://www.boost.org/doc/libs/1_60_0/doc/html/boost_units.html <http://www.boost.org/doc/libs/1_60_0/doc/html/boost_units.html>) available in Swift.
> Yes, that’s an excellent design.  We really want to do this when we get the necessary language features (I hope we might also come up with some that improve readability a bit over what you can do in C++).


So… do you have any thoughts on the matter, Dave? :-)

- Dave

(Is there a way to change my name on the mailing list to “The Other Dave”?)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160112/41996f38/attachment.html>