Karoy Lorentey
Karoy Lorentey
Hm. This package needs these two functions only to work around https://github.com/apple/swift/issues/56105. Fixing that bug would allow the package to remove these, although only if it is compiled using a...
Planning for getting rid of the C module has started in https://github.com/apple/swift-atomics/pull/74. However, this won't land until some Swift compiler & stdlib work is done (and is shipping), so the...
As a stopgap workaround, #95 attempts to switch to using dlsym to access these on Darwin platforms, hopefully bypassing this issue.
#96 and #97 explore two more ways to resolve the problem: hiding the calls inside inline assembly, or using inline assembly directives to smuggle in an extra linkage. Of the...
I verified that #97 will resolve the "symbol not found" issues for `_swift_retain_n` and `_swift_release_n`. However, I'm still seeing subsequent missing symbol issues about `_sa_retain_n` and `_sa_release_n`. These are evidently...
I think the best way forward is to push the `AtomicValue` requirement that `AtomicStorage.Value == Self` down into the `UnmanagedAtomic`/`ManagedAtomic` generics: ```swift public protocol AtomicValue { /// The atomic storage...
Quick update: [@gaetanzanella's sample project](https://github.com/apple/swift-atomics/issues/54#issuecomment-1298599696) has been very helpful in reproducing this. (Thank you!) Unfortunately it's a tooling issue, so the package won't be able to fix it on its...
Getting rid of the C module with something along the lines of https://github.com/apple/swift-atomics/pull/74 would likely also get rid of these issues. However, this will require some Swift compiler & stdlib...
The current `#if __swift__` clauses should nicely step around C compiler problems. Meanwhile, https://github.com/apple/swift-atomics/pull/74 starts walking towards getting rid of the C module altogether. It'll require compiler and stdlib changes...