Michael Tsai on Twitter: "@nuoji Incidentally, this also means that a hypothetical second implementation of the language would need to do all the same optimizations…"

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

Michael Tsai ‏@mjtsai 19 Oct 2014

@nuoji Right. BTW, my understanding is that this sort of thing was once a (lesser) issue in ObjC as well.
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai if you send an NSMutableArray / NSArray as arg, copy only happens on explicit copy. In Swift, this depends on code & optimization.
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai since this is strongly dependent on optimization it ends up unpredictable. This is a very real issue with Swift right now.
Michael Tsai ‏@mjtsai 19 Oct 2014

@nuoji Agreed. Do you think this is fixable?
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai the most worrying part is that issues are patched as they are discovered. It looks like any addition to the lang would then -
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai require additional patches for every special case.
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai compare ObjC where there aren't all that many places where you can optimize.
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai perf is slower than swift in the fastest case, but it is consistent, where Swift easily can differ several orders of magnitude.
Michael Tsai ‏@mjtsai 19 Oct 2014

@nuoji Seems like you have to hope that the compiler never regresses and also that you can figure out what it's doing in pathological cases.
1 like
Christoffer Lernö ‏@nuoji 19 Oct 2014

@mjtsai "Seems like you have to hope that the compiler never regresses" exactly. You need to put your faith in the optimizer. That is scary.

‏@mjtsai

@nuoji Incidentally, this also means that a hypothetical second implementation of the language would need to do all the same optimizations…

11:59 AM - 19 Oct 2014

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.

Michael TsaiVerified account

@mjtsai

Loading seems to be taking a while.

false

Saved searches

Michael TsaiVerified account

@mjtsai

Go to a person's profile

Saved searches

Retweet this to your followers?

Saved searches

Are you sure you want to delete this Tweet?

Promote this Tweet

Block

Add a location to your Tweets

Profile summary

Your lists

Create a new list

Copy link to Tweet

Embed this Tweet

Embed this Video

Preview

Log in to Twitter

Sign up for Twitter

Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

Two-way (sending and receiving) short codes:

Confirmation

Buy Now

Hmm... Something went wrong. Please try again.

Welcome home!

Tweets not working for you?

Say a lot with a little

Spread the word

Join the conversation

Learn the latest

Get more of what you love

Find what's happening

Never miss a Moment

Loading seems to be taking a while.

Promoted Tweet

false