Why the design of operators transform AsyncSequence result long generic names?

[vanvoorden (Rick van Voorden)]

@AlexanderM

The type system can keep the specific type information without erasure (for better optimization), while still giving good human-readable abstractions (-> some AsyncSequence<T>)

How to use `AsyncSequence` on macOS 14.5 in Xcode 16 beta? Need help with availability check since `Failure` is unavailb.e

(I'm using Xcode 16 beta on macOS 14.5) How do I get this to compile for both macOS 15 and macOS 14? : public final class EmitterOfEvents { public typealias Element = Int public func notifications() -> some AsyncSequence<Element, Never> { AsyncStream<Element>.makeStream().stream } } I get error: [Screenshot 2024-06-13 at 11.02.34] I'm well aware of SE-0421, and I'm excited about the change. Hopefully I'm just a bit tired right now and what I want is possible, but it feels like somethi…

FWIW it looks like we might be blocked on an easy solution to return some AsyncSequence if we are deploying to older OS versions.