Brent Simmons
Filed as rdar://22109003
-
@brentsimmons It seems to me the occasional `foo.map({$0})` is a small price to pay for avoiding hidden performance gotchas.
Kevin Ballard
@eridius I’d argue that, instead, there shouldn’t be a hidden performance gotcha.
-
-
@brentsimmons That would be nice, but the only way to solve this without a new array basically requires all protocols to use message-passing -
@eridius Works for me! - View other replies
-
@brentsimmons Message passing is a performance gotcha :P - View other replies
-
@eridius But barely. We can write fast apps in Objective-C. - View other replies
-
@brentsimmons Yeah, but you should be able to write faster ones in Swift. - View other replies
-
@eridius Except for when I have to make an exact copy of an array to satisfy the type system. - View other replies
-
@brentsimmons@eridius Swift arrays are value types, right? So you would be creating a copy even if you returned the same one. - View other replies
-
@PierreLebeaupin@eridius Fine with me. So it should have known how to handle this itself, without the weird map. - View other replies
- Show more
-
-
-
@brentsimmons@eridius I'd say just use NSArray, works with class hierarchies. Swift arrays are like C arrays of structs, not modern types. -
@mdhughes@brentsimmons Swift arrays work with class hierarchies too.
-
Pierre Lebeaupin 
Cyber Mark 2020
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.