chrislattner

9 ms·

61.
by chrislattner 10y ago
Another major advantage: No need for "finalizers" which can often run on an unpredictable thread, resurrect objects, etc. There is extensive literature about how problematic finalizers are in practice. deinit in Swift suffers fr
62.
by chrislattner 10y ago
Some more information is here: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mo... -Chris
63.
by chrislattner 10y ago
I completely agree. Swift's lack of desalinization is a critical problem for users. :-) -Chris
64.
by chrislattner 10y ago
Portability is still a strong goal for Swift 3. I'll revise the page, thanks!
65.
by chrislattner 11y ago
There is a proposal to add support for them - it is currently blocked on infrastructure work necessary to "do it right".
66.
by chrislattner 11y ago
>Just summing floats in an array, compiled without optimization , Ok, so you're both doing it wrong and doing something irrelevant to that level of systems programming. Measuring the performance of non-optimized builds will alwa
67.
by chrislattner 11y ago
I'd be very interested to know what that benchmark is, because you're either doing something very wrong, or it isn't relevant to the systems programming topic being discussed. A 1000x perf difference should be easy to show.
68.
by chrislattner 11y ago
More directly, check out: https://github.com/apple/swift/blob/master/stdlib/public/cor... Which is where much of the Swift "language" is defined... in the standard library. -Chris
69.
by chrislattner 11y ago
Correct. If anything, I'm a founder. LLVM and Clang are much much larger than my own contributions, and I haven't been particularly active lately. That said, I have contributed a lot of code. In LLVM for example, about 20% of