How Swift Achieved Dynamic Linking Where Rust Couldn't

Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by saagarjha on Friday November 08, 2019 @11:23PM (#21489580)

> In the extreme case, we could make a system where everything is an opaque pointer and there's only one function that just sends things strings containing commands.

Interestingly, Objective-C has other ABI issues…

[ Parent | on HN ]

Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by olliej on Friday November 08, 2019 @11:26PM (#21489603)

what are the issues?

[ Parent | on HN ]

Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by saagarjha on Friday November 08, 2019 @11:29PM (#21489616)

ivar layout: http://www.sealiesoftware.com/blog/archive/2009/01/27/objc_e...

[ Parent | on HN ]

Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by dexter0 on Friday November 08, 2019 @11:37PM (#21489646)

The fragile ivar issue is fixed in the modern Objective-C runtime.

[ Parent | on HN ]

Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by saagarjha on Friday November 08, 2019 @11:41PM (#21489666)

Right, non-fragile ivars shipped with the 64-bit runtime as mentioned in the link.

[ Parent | on HN ]