Re: memmove in Swift
Re: memmove in Swift
- Subject: Re: memmove in Swift
- From: "Gerriet M. Denkmann" <email@hidden>
- Date: Thu, 21 Aug 2014 21:12:44 +0700
On 21 Aug 2014, at 16:55, Roland King <email@hidden> wrote:
>
>> My test (using [UInt32] for both Swift and ObjC) showed:
>
> What is [UInt32] for ObjC? A C-array of uint32_t?
Well, the OBj-C sort gets a Swift array and treats it as as a C-array of UInt32. Same as the Swift version.
>> 2. the build-in Swift function sorted(array) crashes with an array of size 10 million and values in the range 0 ... 100. Probably due to excessive recursion.
>> 3. the build-in Swift function sorted(array) with an array of size 10 million and values in the range 0 ... 1000 is about 100 times slower than my own quickSort.
>>
>
> 2) bad, I think I read something on the dev forums about sorted() running out of stack space but I thought that was when run on a thread.
>
> 3) Not brilliant either - what optimization flags were you using for all this?
The default release ones: ObjC: Fastest, Smallest and Swift: Fastest.
Kind regards,
Gerriet.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden