How could that be ABI-stable? We would be going from:
extension LazyCollectionProtocol {
public func split(maxSplits: Int = Int.max, omittingEmptySubsequences: Bool = true, whereSeparator matches: @escaping (Element) -> Bool) -> LazySplitCollection<Elements>
}
in Swift 5 + x to
extension LazyCollectionProtocol {
public func split(maxSplits: Int, omittingEmptySubsequences: Bool = true, whereSeparator matches: @escaping (Element) -> Bool) -> LazySplitCollection<Elements>
public func split(omittingEmptySubsequences: Bool = true, whereSeparator matches: @escaping (Element) -> Bool) -> LazyUnlimitedSplitCollection<Elements>
}
in Swift 6 + x. Would we be hiding the user-level difference between LazySplitCollection and LazyUnlimitedSplitCollection somehow?