Closed TR0NZ0D closed 9 months ago
Isn't this just a side effect of Swift having a proper Observable
type in iOS 17 to support SwiftUI? Namespacing seems to appropriately resolve this, but a collision is inevitable and adding a type alias at a library level for the same collision probably isn't the best approach here.
closing for #202.
Agreed with above, that a global typealias is kicking the issue to other code.
Xcode 15 beta 6+ is failing builds, reported in https://github.com/apple/swift/issues/67815.
@freak4pc's Fix (https://github.com/RxSwiftCommunity/RxSwiftExt/commit/494fe20b5a6bfafb24d6a272fb90a94e1766a6cd) in RxSwiftExt repo for this issue also resolves this problem, which was reported in https://github.com/RxSwiftCommunity/RxSwiftExt/issues/272
trivial