3 ms·
I'm not very familiar with Objective C and Swift, so this might not make sense. But JS used to have a similar problem with async/await. The v8 engine solved it
by felixge 3y ago
I'm not very familiar with Objective C and Swift, so this might not make sense. But JS used to have a similar problem with async/await. The v8 engine solved it by walking the chain of JS promises to recover the "logical stack" developers are interested in [1].
[1] https://v8.dev/blog/fast-async https://v8.dev/blog/fast-async
- astrange 3y agoSwift concurrency does a similar thing. For the older dispatch blocks, Xcode injects a library that records backtraces over thread hops.