@siracusa@mastodon.social Re: ATP Dev. I recently wrote a blog post how we make Swift Errors for our Mac app. Focussing on both the end user and the developer experience. https://nonstrict.eu/blog/2026/the-four-audiences-of-swift-errors/
Remote
Tom Lokhorst
@tomlokhorst@mastodon.social
mastodon 4.8.0-nightly.2026-10-06Indie developer.
Currently working on iPhone mirroring app https://getbezel.app and Vision Pro app https://splitscreen.vision
Fan of both space and time.
0 Followers
0 Following
15 Posts
Joined October 28, 2022
Work:
Personal:
Location:
The Netherlands
WWDC Index:
Transcript of Meet with Apple Q&A on Swift concurrency. https://nonstrict.eu/wwdcindex/meet-with-apple/276/
I wrote a blogpost about how we create Error types in Swift for @bezelapp@mastodon.social. We support fully localized error messages and also want to be able to easily debug and log errors. https://nonstrict.eu/blog/2026/the-four-audiences-of-swift-errors/
People complain about the corner radius of windows on macOS Tahoe. But @bezelapp@mastodon.social shows iPhone hardware as windows, it has always had giant corners.
Now experimenting with the cursor following the curvature of the window exactly.
I’m at @appdevcon@mastodon.social to give a talk about Swift Concurrency and actors. Excited!
Replying to
@mattiem Not fully. The mutating func is modifying the buffer var in the class simultaneously. But I don't know why this triggers this particular crash, at this location.
It also depends on the OS version, on macOS 26 it's the new xzone malloc, but on macOS 15 it sometimes fails with "Fatal error: UnsafeMutablePointer.initialize overlapping range".
https://github.com/nonstrict-hq/StructQueueCrash
Weird crash in Swift "Object of class _ContiguousArrayStorage deallocated with non-zero retain count 2."
I had some old code which tries to protect its internal state using a DispatchQueue. But it's a struct.
When I access it from multiple threads at the same time via a class, it crashes. In my old Swift 5 code I didn't have the "unchecked Sendable", and I assumed it was correct because of the DispatchQueue.
My actual fix is changing the struct to a final class.
It is that time of year again where I point a camera at a wall clock for a long duration recording. To check if the video drift is a bug in the camera driver or my software.
Great talk by @dgregor79@sfba.social on Progressive Disclosure in Swift. https://www.youtube.com/watch?v=opqKGgJavkw
I liked the reworking of non-throwing functions to be syntactic sugar for `throws(Never)`
On Progressive Disclosure in Swift - Doug Gregor - Swift Craft 2025
Replying to
@mattiem Now it’s public.
I think serial queue has same issue. The concurrent queue was just there because that was in my original code.
Replying to
Upgraded my audio/video sync timing testing setup. Now it can run autonomously. Although the beeps are getting annoying.
Replying to
@sjoerd_visscher I was thinking about that. If crappy microphones can pick it up, that would be a good improvement.