4 ms·
The opaque return types are, however, only available in Swift 5.1 and later, which means that the API will have to be different and not directly compatible with
by ajconway 7y ago
The opaque return types are, however, only available in Swift 5.1 and later, which means that the API will have to be different and not directly compatible with the Swift UI.
- cheez 7y agoAs long as Swift supports #ifdefs, I'm sure with some minor coding conventions, they could make it work.
- lilyball 7y agoNot just Swift 5.1, but they also require iOS 13 because there's a rather unfortunate stdlib dependency. Technically they only need the dependency when crossing module boundaries, but they're restricting the feature completely anyway, I guess because they don't want to bother explaining "you can use 'some' on internal APIs but you can't use it on a public API without iOS 13+".