How Swift Achieved Dynamic Linking Where Rust Couldn't A look at what's required to ship a dynamically linked system interface, the most interesting parts of Swift's stabilized ABI, and their incredibly ambitious resilient library evolution system https://gankra.github.io/blah/swift-abi/
There was a series of notes from academia I can’t find offhand that I consulted around the time. It also came to the conclusion that JITs are probably the best solution, though acknowledged tons of tradeoffs.
-
-
(BTW Swift’s approach is called “intensional type analysis” in the literature)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.