My app, #PDXTransit, turns 10 years old this year this August. I wrote it when I moved to Portland back in 2015.
Well, this year for its 10th birthday, I plan to release a complete re-write using the latest technologies from Apple including an iPad-specific user experience.
Here's a sneak peek at what I've been working on the past few years with #SwiftUI, #SwiftConcurrency, and #SwiftData!!!
(and of course it comes with a re-write of its companion app for Apple Watch!)
Swift Concurrency question. I'm trying to get a replacement for Combine's CurrentValueSubject to work but no luck. Any ideas?
You know... Actor-isolated instance method 'makeAsyncIterator()' cannot be used to satisfy nonisolated protocol requirement.
I think I can put a Task into the continuation Callback, but is it a good idea?
#swiftconcurrency #swift
This is by far the most understandable introduction to #swiftconcurrency I have read. https://mastodon.social/@mattiem/112960443757305197
Speaking of first steps with #swiftconcurrency, is it reasonable assumption that, in place of a class that acts as a manager for a system API (like AVSpeechSynthetizer) I would create an actor?
I suppose that switching to the Swift 6 language mode makes turning on strict #swiftconcurrency checking redundant, am I right?
Anyone used NSUndoManager with #SwiftConcurrency? I've now got all my business logic running on its own actor, which uses a custom serial queue (so is not on the main thread). I'm running into conceptual issues:
* I'd really like to use the same undomanager that SwiftUI uses, but that one is presumably main thread confined?
* When registering e.g. a redo operation, you have to perform that registration while the undo manager is undoing. So using a task inside the undo op would not work…
