Swift 3.0 Unsafe World

Re:Swift 3.0 Unsafe World by masklinn on Tuesday September 27, 2016 @11:11AM (#12590185)

> This is because the GC will move objects around in memory

Not necessarily, you could use (and guarantee) a non-moving GC. Moving is but one of the attributes/details you can use for your GC.

[ Parent | on HN ]

Re:Swift 3.0 Unsafe World by mikeash on Tuesday September 27, 2016 @01:48PM (#12591483)

And this is definitely not just theoretical. Any conservative collector must also be non-moving. The Boehm GC for C and C++ and Apple's GC for Objective-C are both existing examples.

[ Parent | on HN ]

Re:Swift 3.0 Unsafe World by masklinn on Tuesday September 27, 2016 @02:11PM (#12591652)

IIRC Go's GC is also non-moving for now (or has that changed in a recent version? I believe it was still non-moving around 1.5)

[ Parent | on HN ]