Brent Simmons
@eridius It just has to check once that EmailMessage is a NodeRepresentedObject. It shouldn't have to check for each item.
-
@brentsimmons Yeah, but you should be able to write faster ones in Swift.
Kevin Ballard
@eridius Except for when I have to make an exact copy of an array to satisfy the type system.
-
-
@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
-
@brentsimmons@PierreLebeaupin `foo as bar` should never be expensive. More importantly, silent coercions should never be expensive either.
-
-
-
@brentsimmons@eridius Think of it this way: in C, `int foo() { int i = 12; return i; }` creates a copy of i and returns it. -
@brentsimmons@eridius (Perhaps a struct-returning function would be a better example.)
-
-
-
@brentsimmons The elements in the array are the same, but the array is not. Some types storable in [NRO] can't be put in [EM]@eridius - View other replies
-
@Callionica@brentsimmons That's irrelevant. Arrays in Swift are value types, not reference types, so mutation doesn't affect it. -
@eridius Swift array has state-changing members so type-checker complains, no?@brentsimmons -
@Callionica@brentsimmons Array is a value type so mutations to a `[Foo]` can't possibly be visible in a `[Bar]` as they are distinct values
-
Pierre Lebeaupin 
Kyle S.
Callionica
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.