Michael Tsai on Twitter: "@mpweiher Separate class, separate methods names is fine. But then no reason to subclass. Also, fast enumeration won’t work."

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

Joe Groff ‏@jckarter May 30

@mpweiher @phink0 @mjtsai Array and Dict needed to be able to contain unboxed value types; String needed efficient copy-on-write.
1 like
Marcel Weiher ‏@mpweiher May 30

@jckarter @phink0 @mjtsai s/need/want/g
Guy English ‏@gte May 30 San Diego, CA

@mpweiher @jckarter @phink0 @mjtsai I think that's a pretty reasonable thing to want. It's hardly some crazy boondoggle.
1 like
Marcel Weiher ‏@mpweiher May 30

@gte @jckarter @phink0 @mjtsai (a) not that hard to add to NSArray if you want (b) NXStorage anyone? (c) MPWRealArray and friends [SOA>AOS]
2 likes
Joe Groff ‏@jckarter May 30

@mpweiher @gte @phink0 @mjtsai Swift.Array's buffer is in fact an NSArray subclass, so that interop is cheap.
2 likes
Marcel Weiher ‏@mpweiher May 30

@jckarter @gte @phink0 @mjtsai Yes. Point was that additional layering (causing slowdowns) is choice, not necessity.
Marcel Weiher ‏@mpweiher May 30

@jckarter @gte @phink0 @mjtsai And it seems obvious that that NSArray subclass can do all the things you want from it. Or not?
1 like
Michael Tsai ‏@mjtsai May 30

@mpweiher @jckarter @gte @phink0 An NSArray subclass is limited by the interface requiring everything to be an object.
1 like
Michael Tsai ‏@mjtsai May 30

@mpweiher @jckarter @gte @phink0 Obj-C generics don’t address this. What use is a subclass if all the method names are different?
Marcel Weiher ‏@mpweiher May 31

@mjtsai @jckarter @gte @phink0 Since you can’t mix and match anyway (single type), how is different method names a problem? And if you …
1 like

‏@mjtsai

@mpweiher Separate class, separate methods names is fine. But then no reason to subclass. Also, fast enumeration won’t work.

5:17 AM - 31 May 2016

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