Karoy Lorentey
Karoy Lorentey
This does work well, but I don't expect we'll land it in this form. We are planning to radically streamline the `AtomicValue` protocol for the stdlib proposal, and I expect...
It looks like these attributes have been present since 5.6, so we can safely add them once #67 lands.
Ah, `@_noLocks` and `@_noAllocation` require the `-experimental-performance-annotations` compiler flag. Unfortunately the package manager considers such flags "unsafe", so this package cannot use them. 😞
`Sendable` has no ABI impact -- we can simply add the conformance whenever we are ready!
I'll see if I can add a commit to this PR to make it work in all configurations of System later today!
(I expect this will fail on Swift 5.7, possibly 5.8.)
@swift-ci test
That's not ideal. - What platform are you targeting? - Can you step me through your build setup? In particular, did you do any custom configuration to have this package...
@kimdv Yep, that's quite clear. SwiftPM's Xcode integration should not ever generate invalid bundle identifiers -- so the cause is clearly a tooling bug. However, the only way we can...
I see a warning when I try reproducing this: ``` Module 'HeapModule' was not compiled with library evolution support; using it means binary compatibility for 'TestFramework' can't be guaranteed ```...