airspeedswift

29일 전discuss

You can choose to use either refcounting or unique ownership for your types. For most use cases, refcounted (+ copy-on-write) is the best choice and is the default, but the truetype interpreter made extensive use of non-refcounted types to achieve this performance.

airspeedswift

29일 전discuss

I assure you, every inch of the interpreter code has been stared at by humans, a lot. TBH even the assembly generated by it has.

airspeedswift

8개월 전discuss

Python and LIT are used heavily to build and test the compiler, but that is only for building it, you do not need it to download and use the built toolchain. The python dependency is more about its use in LLDB.

airspeedswift

8개월 전discuss

The Swift toolchain includes LLDB, which relies on python for some debugging features. The compiler and runtime itself do not use python.

airspeedswift

9개월 전discuss

> e.g kotlin exceptions cant be caught from swift

FWIW the approach that swift-java takes in managing interop with Java (and potentially Kotlin) function calls means it is perfectly possible to to catch exceptions thrown by the JVM using wrappers that catch and rethrow them as Swift errors. So there would be a distinction here with bringing Swift calling into JVM-based code running on Android.

comments