Ohh a simpler and safer continuation type!
06.03.2026 11:21
👍 10
🔁 1
💬 0
📌 0
This can be a very hard mode to support.
I *think* a big part of it is indicating "this protocol cannot be used only from the MainActor", which you express with a conformance to SendableMetatype.
But I'm interested in specific examples of things you are running into! Please share!
Does this mean you have public protocols that you want to keep compatible with clients using MainActor by default, or that your library is using it?
Ah!
So there are no edge cases I'm aware of here. You make the API you want. If you want to give clients the ability to use it without checks, you add "@.preconcurrency" to your public APIs. I don't think 6.2 changes anything about this…
We're fuelling up for another year of SwiftLeeds, and we need YOU in the cockpit.
Whether you want to talk about SwiftUI, Swift concurrency, server-side Swift, accessibility, or something we haven't even thought of — we'd love to see your submission.
Submit your talk idea → swiftleeds.co.uk/cfp
So, if anyone out there knows someone who knows someone who's looking for someone who is an experienced engineer, and is also a very good communicator and designer and guy-who-actually-understands-how-to-make-products-good...let me know.
After a thoughtful nudge, I have renamed my "Lock" package to use the term "Gate". And while I was in there, I updated a bunch of things, including finally getting a recursive gate working!
I have found this kind of tool incredibly useful for managing actor reentrancy with Swift Concurrency.
Same
Marisa is legit. Please share if you know someone she can talk to.
It's a pretty esoteric thing, but I had to call it out because it's so nice to see small things get fixed. The mysterious JamieQ saves the day yet again.
Very basic, just playing around with NetNewsWire…
Not yet!
I think I may be an RSS person now
Ohhh that's a very interesting point!
While I am inclined to agree, it is technically possible to remove "temperature" and make LLM output deterministic. It makes it much worse, if I understand right, but it is a fascinating aspect.
😆
I attempted to tackle this question here, in case it is interesting
If you ask me to solve a problem for you, do I become a tool?
Content-addressable memory!
Is non-artificial intelligence a tool?
I find the idea that AI is a compiler or abstraction very strange. But I do think "delegation" is getting closer.
(I still don't buy that it is a "tool", even if it can be used like one.)
The cocoaheads group there was amazing, and worth checking out
Ok I understand what you were all saying about Subnautica now
I was not even aware of trailers until now. Thanks, I hate it too.
Was definitely not clear!
I'm observing that a large percentage of new swift packages have generated readmes with lists of features that are part of the compiler and not the package itself.
I enjoyed it! But I do get what you are saying.
🚀 valid syntax
✅ completely type-safe
🔐 full actor isolation
📦 uses Package.swift
I think it's important to listen attentively and really try to understand a different perspective before yelling "WRONG WRONG NO NO WRONG"
Yes! I want all battery levels on all devices!
I very much agree it is overwhelming and uncertain.
