On Fri, Sep 19, 2014 at 2:05 AM, Quinn "The Eskimo!" <email@hidden> wrote:
>
> On 18 Sep 2014, at 22:58, Paul Stevenson <email@hidden> wrote:
>
> > Anyone know the reasons for making that change, rather than expanding vtable support to include arm?
>
> My understanding is that the optimisations that were done as part of the ARC effort eliminated the performance advantages derived from vtables.
You mean something like that retain/release/autorelease were three of
the most important vtable selectors, and they're mostly now not called
via method dispatch since objc_retain()/objc_release()/etc
short-circuit to the NSObject implementations for almost all objects?
I'm a bit surprised that selectors like isEqual:, objectAtIndex: (or
more recently, objectAtIndexedSubscript:) and isKindOfClass: weren't
worth the cost
of vtabling.
Paul
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Objc-language mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
