[swift-users] Need help with compile times (type inference?)
dturnbull at gmail.com
Tue Jan 26 11:57:11 CST 2016
Awesome! Any attention is appreciated.
I tried the 3.0-dev snapshot from yesterday. The ortho example is slower
than 2.2-dev which is slower than 2.1.
If you get compiler crashes, comment out the any() and all() functions. I
opened a bug on this.
If I can help, please let me know.
On Mon, Jan 25, 2016 at 10:49 AM, Joe Pamer <jpamer at apple.com> wrote:
> Thanks for sharing, David!
> As JoeG mentions below, I’ve been rolling out a series of major
> improvements in this area. I’ll take a look at SwiftGL to see what else can
> be done.
> - Joe
> On Jan 25, 2016, at 12:59 AM, David Turnbull via swift-users <
> swift-users at swift.org> wrote:
> On Sun, Jan 24, 2016 at 9:55 PM, Chris Lattner <clattner at apple.com> wrote:
>> Are you willing/able to share the code for your project? That definitely
>> sounds strange,
> Soitenly: https://github.com/AE9RB/SwiftGL
> The 28,000 lines of loader code are fine. The 6,000 lines of math
> libraries are the problem.
> I'm sure it's something to do with prototypes and generics. You can change
> in Types.swift:
> public protocol FloatingPointScalarType : ScalarType
> public protocol FloatingPointScalarType : ScalarType, FloatingPointType
> and make the problem a bit worse. This is something I'd actually like to
> use, except I don't because a few "where constraints" do what I need
> without the build slowdown.
> Swift 2.1 or 2.2-dev doesn't make a difference. The C++ compiler I bench
> against is also llvm. The compiled binaries are truly fast (with WMO). It's
> only the development process that's too slow because of build times.
> -David "nyuk nyuk nyuk" Turnbull
> swift-users mailing list
> swift-users at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-users