Christoffer Lernö
.@mjtsai I think the problem you identified in your blog entry permeates Swift - trading predictable runtime perf for "the correct way".
-
.
@mjtsai you OFTEN want the way Swift acts but it is not explicit, and something I always try to avoid is code that isn't obvious enough.
Michael Tsai@nuoji Why do you say "not explicit"? Because the "var" may be textually far away?
-
-
@mjtsai var arrays will try to optimize for you, so the actual runtime perf and behavior will depend on subtle variations to your code. -
@nuoji Yes, agreed about the perf being more hidden. I thought you were talking about "explicit" when reading the code. -
@mjtsai compare ObjC - switching between mutable and immutable is completely explicit and inspectable. Including when passing arrays as args - View other replies
-
@nuoji Aren't "var" and "inout" just different ways of spelling "mutable"? That's explicit. -
@mjtsai it only describes the language rules, it does not describe the behavior of the underlying runtime. - View other replies
-
@nuoji Right. BTW, my understanding is that this sort of thing was once a (lesser) issue in ObjC as well. -
@mjtsai if you send an NSMutableArray / NSArray as arg, copy only happens on explicit copy. In Swift, this depends on code & optimization. - View other replies
-
@mjtsai since this is strongly dependent on optimization it ends up unpredictable. This is a very real issue with Swift right now. - Show more
-
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.