Thank you for your reply! I filed FB11893691 with a minimal sample project to reproduce this. Would be awesome if you could find anything!

Whatever you did, it worked! The issue is gone in the latest macOS 13.2 Beta. Thank you!

@Claude31: See the WWDC23 session that I tagged: Generalize APIs with parameter packs. The feature is explained there. And in the Swift Evolution proposal, of course: Value and Type Parameter Packs.

You’re right that this could just be a bug or at least something that hasn’t been implemented yet. After all, functions can only declare a single parameter pack, so there shouldn’t be any ambiguity as to how many times anything should be repeated.

(I removed this comment and posted it as a reply below for truncation reasons)

(I removed this comment and posted it as a reply below for code formatting reasons)

That is a possible solution if all you need is a SwiftUI Image as a SwiftUI view, but that won’t help if you actually want to do anything with the image. AFAICT, there’s no way to get to an image’s data from a SwiftUI Image. I guess this is also the reason why it can be marked as Sendable: SwiftUI guarantees that the properties that are not thread safe will only ever be accessed on the main thread and since SwiftUI is the only thing that has access to that, it can ensure that.