Re: [Haskell-cafe] Automatic Reference Counting

2011-07-06 Thread David Barbour
On Tue, Jul 5, 2011 at 9:00 PM, steffen wrote: > The important point about reference counting on idevices is the near > realtime performance, since stops for collecting garbage are actually very > short in comparison to collecting compilers (despite more frequent). You can get near realtime perf

Re: [Haskell-cafe] Automatic Reference Counting

2011-07-05 Thread steffen
The important point about reference counting on idevices is the near realtime performance, since stops for collecting garbage are actually very short in comparison to collecting compilers (despite more frequent). Some compilers, I think it was for the pure functional programming language OPAL i

Re: [Haskell-cafe] Automatic Reference Counting

2011-07-05 Thread Maarten Hazewinkel
On 2 Jul 2011, at 18:35, Thomas Davie wrote: > > It's interesting that you cite that GC is both faster and lower memory > overhead – Apple's stated reasons for implementing this were that GC was both > too slow and too memory intensive to use sensibly on iDevices and that ARC > was both faster

Re: [Haskell-cafe] Automatic Reference Counting

2011-07-02 Thread Thomas Davie
On 2 Jul 2011, at 17:52, Chris Smith wrote: > On Sat, 2011-07-02 at 17:35 +0100, Thomas Davie wrote: >> It's interesting that you cite that GC is both faster and lower memory >> overhead – Apple's stated reasons for implementing this were that GC >> was both too slow and too memory intensive to u

Re: [Haskell-cafe] Automatic Reference Counting

2011-07-02 Thread Chris Smith
On Sat, 2011-07-02 at 17:35 +0100, Thomas Davie wrote: > It's interesting that you cite that GC is both faster and lower memory > overhead – Apple's stated reasons for implementing this were that GC > was both too slow and too memory intensive to use sensibly on iDevices > and that ARC was both fas

Re: [Haskell-cafe] Automatic Reference Counting

2011-07-02 Thread Steve Schafer
On Sat, 2 Jul 2011 16:51:53 +0100, you wrote: >Apple recently announced a new static analysis in Clang called ARC >(Automatic Reference Counting). The idea is to provide what GC >provides (zero memory management code by the programmer), but not to >incur the runtime penalty of having to have the

Re: [Haskell-cafe] Automatic Reference Counting

2011-07-02 Thread Thomas Davie
On 2 Jul 2011, at 17:18, Thomas Schilling wrote: > Reference counting usually has much higher overheads than garbage > collection and is tricky to parallise. It's main advantage is quicker > release of memory. > > I believe the main feature of ARC is that the user does not need to > manually ke

Re: [Haskell-cafe] Automatic Reference Counting

2011-07-02 Thread Thomas Schilling
Reference counting usually has much higher overheads than garbage collection and is tricky to parallise. It's main advantage is quicker release of memory. I believe the main feature of ARC is that the user does not need to manually keep reference counts up to date. I heard from people using CPyt

[Haskell-cafe] Automatic Reference Counting

2011-07-02 Thread Thomas Davie
Hi guys, Apple recently announced a new static analysis in Clang called ARC (Automatic Reference Counting). The idea is to provide what GC provides (zero memory management code by the programmer), but not to incur the runtime penalty of having to have the GC run. It seems to be extremely effe