mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,4 Tsd.
aktive Profile

#swiftconcurrency

0 Beiträge0 Beteiligte0 Beiträge heute
Fortgeführter Thread

🗓️ Saturday, July 5, 11:30am Pacific, 18:30 UTC
Swift Concurrency, Group Learning Session: Parallelization of Tasks

In this session, we will be investigating and leveraging parallelization of tasks. Specifically, we will attempt to parallelize rendering of map tiles in the CubiomesKit project.
#SwiftConcurrency #SwiftDev #AppleDev
discord.gg/euyXVzzX?event=1388

DiscordTritt dem Swift Dev Chat-Discord-Server bei!Software developers, hobbyists, and learners, using the Swift programming language. | 258 Mitglieder

🗓️ Saturday, July 5, 11:30am Pacific, 18:30 UTC
Swift Concurrency, Group Learning Session: Parallelization of Tasks

In this session, we will be investigating and leveraging parallelization of tasks. Specifically, we will attempt to parallelize rendering of map tiles in the CubiomesKit project.
#SwiftConcurrency #SwiftDev #AppleDev

discord.gg/nyXRvBC5tS?event=13

DiscordTritt dem Swift Dev Chat-Discord-Server bei!Software developers, hobbyists, and learners, using the Swift programming language. | 257 Mitglieder

✨Swift 6.2 ✨

SE-0481 is introducing "weak let" to Swift 6.2!

That will allow us to create immutable weak references that can't be reassigned after initialization, but can still become nil when the referenced object is deallocated.

This is a game-changer for Sendable compliance (weak var can't be Sendable, but weak let can!) 🎉

#Swift #iOS #SwiftConcurrency #SwiftLang

github.com/swiftlang/swift-evo

GitHubswift-evolution/proposals/0481-weak-let.md at main · swiftlang/swift-evolutionThis maintains proposals for changes and user-visible enhancements to the Swift Programming Language. - swiftlang/swift-evolution

📣 #iOSDev PSA: new #Xcode26 projects default to Main Actor isolation, which can lead to errors with Sendable types ⚠️

Possible Fixes:
1: Change default isolation
2: Mark type as nonisolated
3: Ignore #SwiftConcurrency 🫣

@mattiem has a great post on default isolation: massicotte.org/default-isolati

Quite frankly, if I hadn't read your post before, I probably would've taken a lot longer to figure out why the heck the type in question was MainActor isolated to begin with - thanks Matt! 👏

🚨 New Premium Workshop!

“Concurrency Fundamentals with Swift 6.2”
w/ @mattiem
🗓️ Sunday, June 8 | 🕐 1–4 PM
📍 Cupertino, CA
🎟️ Sign up: buff.ly/R921TWg

Matt Massicotte has taught private workshops for over 60 engineers, and his contributions to Swift Concurrency are widely respected by Apple devs.

Best of all, Matt is generously donating all proceeds to support OMT’s free community programming throughout WWDC week ❤️

#SwiftLang#Swift#AppleDev

Reminder: Group learning session on the Swift Dev Chat Discord server.
🗓️ This Saturday, May 24, 11am Pacific, 18:00 UTC.

Participate in “ensemble coding” as we (try to) apply strict Swift Concurrency to an existing open source project (XcInspector—SwiftUI app on macOS, plus command-line tool).
All experience levels welcome—as long as you’re wanting to learn more about programming in Swift.
#SwiftUI #SwiftConcurrency
discord.gg/sGM552KyMn?event=13

DiscordTritt dem Swift Dev Chat-Discord-Server bei!Software developers, hobbyists, and learners, using the Swift programming language. Especially on Apple platforms. | 260 Mitglieder

Group learning session on the Swift Dev Chat Discord server.
🗓️ Saturday, May 24, 11am Pacific, 18:00 UTC.

Participate in “ensemble coding” as we (try to) apply strict Swift Concurrency to an existing open source project (XcInspector—SwiftUI app on macOS, plus command-line tool).
All experience levels welcome—as long as you’re wanting to learn more about programming in Swift.
#SwiftUI #SwiftConcurrency
discord.gg/sGM552KyMn?event=13

DiscordTritt dem Swift Dev Chat-Discord-Server bei!Software developers, hobbyists, and learners, using the Swift programming language. Especially on Apple platforms. | 260 Mitglieder

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

I did not know that turning on "Strict Concurrency Checking" (without changing swift version) could change the actual runtime instead of just compile-time warnings. Found a bug that was driving me crazy (FB15391171).

Xcode 16 Beta 1 + Strict Concurrency on: `async let`, when ran on a synchronous function, runs on the current actor instead of the expected background executor. Does not happen on 16. It's one of those "is my mental model wrong again" bugs 😅 #swiftconcurrency

One annoyance of SwiftConcurrency is that it prioritizes isolation over parallelism in its vocabulary. I want code to run “in the background" AKA “not block the main thread” but all we have is “stuff is isolated or not isolated but no guarantees in what thread it'll end up except if it's MainActor”-concepts.

Like now, I have a nonisolated async function awaiting a ModelActor created in said function, and the model actor code runs on the main thread. In other instances where I do the same thing, it runs in a background thread. Why? I don't know, but the ModelActor doc only says that it “provides mutually exclusive access to attributes of a model” without any other guarantees, so I guess I should expect this to sometimes happen.

developer.apple.com/documentat

I want more parallelism guarantees, maybe make a BackgroundActor guaranteed to never run on the main thread, possibly using the word “main thread” in the doc.

Apple Developer DocumentationModelActor | Apple Developer DocumentationAn interface for providing mutually-exclusive access to the attributes of a conforming model.

If folks are looking for using Swift Testing with Vapor, you'll encounter all sort of issues.

Here is something that might help you getting out of troubles:
github.com/vapor/vapor/issues/

It's using Lock from @mattiem ; of course. Who would imagine solving a swift concurrency issue without Matt work on it? 😜

GitHubSwift Testing support: ServeCommand did not shutdown before deinit · Issue #3236 · vapor/vaporVon Dean151
#Swift#Vapor#SwiftTesting