andyfinnell - Network

TIL: CATiledLayer and Swift Concurrency do not mix.I did the trick where UIView.layerClass returns CATiledLayer.self so my (large) UIView is...

TIL: CATiledLayer and Swift Concurrency do not mix.

I did the trick where UIView.layerClass returns CATiledLayer.self so my (large) UIView is performant. But that means parts of UIView now get called on background threads, and Swift._checkExpectedExecutor() gets all assert-y.

Not sure if there's a way around this.

*sigh*This is just yet another sign I'm getting old and curmudgeonly. I _strongly_ prefer predictable over "magical”.

*sigh*

This is just yet another sign I'm getting old and curmudgeonly. I _strongly_ prefer predictable over "magical”.

Confession: web browser tab management confuses the heck outta me. When I open a new tab or close the tab I'm on, I have literally no...

Confession: web browser tab management confuses the heck outta me. When I open a new tab or close the tab I'm on, I have literally no idea where the browser is going to take me. It might as well be RNG.

The thing is, the behavior is sophisticated enough that there must have been tons of UX research into how build this. All thwarted because I'm too old and/or stupid to understand their algorithm. Sorry I let you down.

Can I make KeyPaths work with async properties at all? Compiler seems to imply "no" but I can't find any discussions about...

Can I make KeyPaths work with async properties at all?

Compiler seems to imply "no" but I can't find any discussions about this when googling.

On the other hand, if you do something boneheaded (which is apparently a preferred pastime of mine) and ask a `Picker` to select a value...

On the other hand, if you do something boneheaded (which is apparently a preferred pastime of mine) and ask a `Picker` to select a value that's not _in_ the `Picker`, it'll emit a helpful console message telling you that, along with the missing tag. Helpful!

SwiftUI’s `Picker` has multiple selection support via its `init(_:sources:selection:)` constructor, which is incredibly useful....

SwiftUI’s `Picker` has multiple selection support via its `init(_:sources:selection:)` constructor, which is incredibly useful. Unfortunately, I've discovered if `sources` ever goes empty it just crashes with nary a log message or indicator as to why.

I just wrote my first test using the new Swift Testing framework. Pleased to report it did _not_ crash the compiler. (Although the day is...

I just wrote my first test using the new Swift Testing framework. Pleased to report it did _not_ crash the compiler.

(Although the day is still young)

lol, I shouldn't have said anything. As soon as I try to instantiate said type that uses parameter pack iteration, compiler crash.

lol, I shouldn't have said anything. As soon as I try to instantiate said type that uses parameter pack iteration, compiler crash.

Parameter pack iteration in Swift 6 is all I hoped it could be. https://www.swift.org/blog/pack-iteration/

Parameter pack iteration in Swift 6 is all I hoped it could be.

https://www.swift.org/blog/pack-iteration/

...and with that, this small side project (a few thousand lines of Swift) is fully Swift 6. Took about a day's worth of work.The big...

...and with that, this small side project (a few thousand lines of Swift) is fully Swift 6. Took about a day's worth of work.

The big things were macros (crasher + updating to new SwiftSyntax) and concurrency. Strict concurrency on 5.10 had gotten me pretty far, but not all the way.

…ok, a bit of an exaggeration. More like 50%.

…ok, a bit of an exaggeration. More like 50%.

90% of my assertMacroExpansion unit tests fail because of whitespace changes caused by updating SwiftSyntax to 6.

90% of my assertMacroExpansion unit tests fail because of whitespace changes caused by updating SwiftSyntax to 6.

Parameter packs still appear to be non-Sendable even if contained types are. See https://github.com/swiftlang/swift/issues/74484However, the...

Parameter packs still appear to be non-Sendable even if contained types are. See https://github.com/swiftlang/swift/issues/74484

However, the work around in this Stack Overflow appears to work: https://stackoverflow.com/questions/78618908/swift-parameter-packs-and-sendable

Basically, expand out into tuple, send that across concurrency boundaries since tuples are Sendable, then repeat each the tuple.

`DispatchData` is not Sendable

`DispatchData` is not Sendable

Answer: add in `Sendable` conformance to the key path type:func myFunc(keyPath: WritableKeyPath<Value, ToValue> & Sendable)

Answer: add in `Sendable` conformance to the key path type:

func myFunc(keyPath: WritableKeyPath<Value, ToValue> & Sendable)

In Swift 6, what's the correct way to deal with KeyPaths not being Sendable? I can find lots of comments online (and hacks), but...

In Swift 6, what's the correct way to deal with KeyPaths not being Sendable? I can find lots of comments online (and hacks), but it's not clear what the "blessed" path is.

Wait… in Swift 6 can I call an actor's instance method from the init without an `await`???…I guess that's a yes. It compiles and...

Wait… in Swift 6 can I call an actor's instance method from the init without an `await`???

…

I guess that's a yes. It compiles and does not crash at runtime. Nice!

My fix was to have my conformance macro explicitly list both parent and child protocols

My fix was to have my conformance macro explicitly list both parent and child protocols

I finally figured the crash out, but I’m bewildered. I have protocol SubProtocol which subtypes ParentProtocol. I have a macro which...

I finally figured the crash out, but I’m bewildered. I have protocol SubProtocol which subtypes ParentProtocol. I have a macro which conforms TypeA to SubProtocol (and thus ParentProtocol).

If I write a generic method over a type implementing SubProtocol and pass in TypeA Swift gives confusing errors, but eventually tells me TypeA doesn't declare conformance to ParentProtocol (?!??!)

If a _macro_ writes the said generic method from the previous paragraph, the whole Swift compiler crashes.

I was looking forward to upgrading this side project to Swift 6 to see how my strict concurrency work had fared. But no, now I get to go...

I was looking forward to upgrading this side project to Swift 6 to see how my strict concurrency work had fared. But no, now I get to go debug the Swift compiler's macro code generation.