You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When `String` started to conform to `Collection`, `flatMap` had to be overloaded to provide backward compatibility for a few cases. See this PR: #9466
Now that `compactMap` has been introduced instead of the problematic variant of `flatMap`, it should be possible to remove those overloads, since there had been no `compactMap` usages that need to be supported.
Additional Detail from JIRA
md5: 72669eaea0fb8753b3a5459a0231bba1
Issue Description:
When `String` started to conform to `Collection`, `flatMap` had to be overloaded to provide backward compatibility for a few cases. See this PR: #9466
Now that `compactMap` has been introduced instead of the problematic variant of `flatMap`, it should be possible to remove those overloads, since there had been no `compactMap` usages that need to be supported.
See relevant discussion here: https://forums.swift.org/t/why-is-there-a-collection-flatmap-that-takes-a-closure-returning-string/10141
The text was updated successfully, but these errors were encountered: