Optimization - eliminated costly [NSNumber floatValue] calls #232

Closed
wants to merge 1 commit into from

4 participants

@thomas-brx

[NSNumber floatValue] is expensive, this patch removes the need for floatValue during animations by using an array of floats in an NSData container instead.

@Panajev

Since animation should not change in size (frame count), the need for an auto growing NSMutableArray object is really not there. Do you see cases in which one would need that flexibility? If not, this is an easy and effective optimization.

@Zakay

+1

@Birkemose Birkemose closed this Mar 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment