_StringProcessing overload for Collection.split(separator:maxSplits:omittingEmptySubsequences:)

as of the June toolchain, it seems like _StringProcessing is vending an extension method Collection.split(separator:maxSplits:omittingEmptySubsequences:) that is identical to one in the Swift module.

  1. sSl17_StringProcessingSQ7ElementRpzrlE5split9separator9maxSplits25omittingEmptySubsequencesSay11SubSequenceQzGqd___SiSbtSlRd__ABQyd__ACRSlF
  2. sSlsSQ7ElementRpzrlE5split9separator9maxSplits25omittingEmptySubsequencesSay11SubSequenceQzGAB_SiSbtF

what is the relationship between the two methods?

_StringProcessing also seems to collide a lot with RegexBuilder, for example:

  1. sSK12RegexBuilderSs11SubSequenceRtzrlE14trimmingPrefixySsqd__yXE17_StringProcessing0A9ComponentRd__lF
func trimmingPrefix<R>(_ content: () -> R) -> Self.SubSequence 
    where R : RegexComponent
  1. sSK17_StringProcessingSs11SubSequenceRtzrlE14trimmingPrefixySsqd__AA14RegexComponentRd__lF
func trimmingPrefix<R>(_ regex: R) -> Self.SubSequence 
    where R : RegexComponent
1 Like