Christoffer Lernö
Marcel Weiher
@nuoji 1000x slower? Wow, that's worse than I would have expected (and I expected bad). Unlikely to change significantly (see C++,Scala etc)
-
-
@mpweiher On my computer compile time is roughly 2.6e-7 * (loc^2) AND swift does a full compile of all swift files every time. -
@nuoji Supposedly separate files become more coupled with all the compiler tech being used,considering perf. results probably not worth it. -
-
@mpweiher I read one project that saw profiling times go down from 1700 ms to 12 ms when fixing an issue using ObjC from Swift -
@mpweiher straightforward Swift code resulted in that 14000% increase in time from normal. https://devforums.apple.com/thread/244975?tstart=0 … -
@nuoji Wow. Expensive default semantics, 100% reliance on optimizer to get remotely reasonable perf., unpredictable performance model. - View other replies
-
@mpweiher wildly predictable, and then at best you get inline C performance. It's worrying.
-
-
-
@mpweiher The mistake you do with Objective-smalltalk is not dressing it in a C++-like syntax. People would have eaten it up. -
@nuoji Well, interop with ObjC becomes so much messier, and Swift's C++ like syntax is also causing other problems. Blog post coming up. - View other replies
-
-
-
@mpweiher I'd love to work on something that would resemble swift in some of the syntax, but build on ObjC like objective-smalltalk. -
@mpweiher In other news, cross-file and all-in-one-file compilation differs by a slowdown of x3-x37 in runtime performance. -
@mpweiher compare compiling ObjC which sanely only compiles the files that changed. -
@mpweiher O(n^2) is especially fun because at 100-1000 lines compile times aren't very noticeable.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.