Michael Tsai on Twitter: "@nuoji Tricky implementations of NSData and NSString to link to other immutable objects when you split/join instead of copying data."

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

Christoffer Lernö ‏@nuoji 19 Oct 2014

.@mjtsai I think the problem you identified in your blog entry permeates Swift - trading predictable runtime perf for "the correct way".
Christoffer Lernö ‏@nuoji 19 Oct 2014

.@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 ‏@mjtsai 19 Oct 2014

@nuoji Why do you say "not explicit"? Because the "var" may be textually far away?
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai var arrays will try to optimize for you, so the actual runtime perf and behavior will depend on subtle variations to your code.
Michael Tsai ‏@mjtsai 19 Oct 2014

@nuoji Yes, agreed about the perf being more hidden. I thought you were talking about "explicit" when reading the code.
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai compare ObjC - switching between mutable and immutable is completely explicit and inspectable. Including when passing arrays as args
Michael Tsai ‏@mjtsai 19 Oct 2014

@nuoji Aren't "var" and "inout" just different ways of spelling "mutable"? That's explicit.
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai it only describes the language rules, it does not describe the behavior of the underlying runtime.

‏@mjtsai

@nuoji Tricky implementations of NSData and NSString to link to other immutable objects when you split/join instead of copying data.

11:30 AM - 19 Oct 2014

Michael TsaiVerified account