# RangeReplaceableCollection **URL:** \ **Category:** Discussion\ **Created:** [August 13, 2019, 5:57am UTC](https://forums.swift.org/t/rangereplaceablecollection/27839 "2019-08-13T05:57:17Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![gwendal.roue](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/gwendal.roue/32/13992_2.png) [@gwendal.roue](https://forums.swift.org/u/gwendal.roue)\ **Post date:** [August 13, 2019, 8:08am UTC](https://forums.swift.org/t/rangereplaceablecollection/27839/5 "2019-08-13T08:08:42Z")
You are right @Avi, you have described the classic sin. But aren't we looking at _another_ sin, then? Consider this [other current discussion](https://forums.swift.org/t/implementing-a-collection-removingindicies/27681/23), which talks about removing indices. What will happen when the Standard Library defines the same extension, and a user imports Foundation? Or, more precisely, if Foundation defines the same extension (after all, `IndexSet` is Foundation's property)? Won't the compiler complain with ambiguity errors, due to two conflicting implementations? Should SwiftUI be allowed to step on Foundation's "natural" territory? --- _[View the full topic](https://forums.swift.org/t/rangereplaceablecollection/27839)._