fix atomic continuation guards#210
Conversation
doozMen
force-pushed
the
fix/atomic-continuation-guards
branch
from
157281e to
649449f
Compare
doozMen
force-pushed
the
fix/atomic-continuation-guards
branch
2 times, most recently
from
55fc9d2 to
9975609
Compare
fix rebase with upstream fix rebase with upstream fix continuation (#9) Co-authored-by: Stijn Willems <stijn@promptping.ai>
doozMen
force-pushed
the
fix/atomic-continuation-guards
branch
from
9975609 to
730cc61
Compare
|
Closing this PR — it bundles too many unrelated changes (platform minimum bump, atomic continuation guards, withBatch generics) without description, tests, or justification. Will file a proper issue upstream documenting the Swift 6.3 compiler error and discuss the right approach. |
doozMen
left a comment
doozMen
left a comment
There was a problem hiding this comment.
sorry for the ai slob was not supposed to be a pr yet. I'm trying to get it build on swift 6.3-dev snapshot but also not sure yet there is a bug this pr was a glitch. sorry
|
Filed #211 as a proper issue with root cause analysis, compiler output, and a suggested fix that preserves the current platform minimums (macOS 13+/iOS 16+) using an NSLock-based wrapper instead of See also #203 for the related |
1 participant
No description provided.