<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi David,<div class=""><br class=""></div><div class="">There were a few instances where this topic or similar came up at the&nbsp;<a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160905/026923.html" class="">Swift Evolution List</a>&nbsp;and&nbsp;<a href="https://lists.swift.org/pipermail/swift-users/Week-of-Mon-20161010/003631.html" class="">Swift Users List</a>.</div><div class=""><br class=""></div><div class="">There’s even&nbsp;<a href="https://github.com/luish/swift-evolution/blob/f99e325484a5b19ce4bab8eda18f284e4e250e7b/proposals/nnnn-more-lenient-collections-subscripts.md" class="">this interesting proposal</a>&nbsp;that dwells with it while providing more lenient subscripts to collections.</div><div class=""><br class=""></div><div class="">BTW, I agree with you, having the range type split is somewhat confusing, specially for those new to the language.</div><div class=""><br class=""></div><div class="">Best,</div><div class=""><br class=""></div><div class="">—A</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 12, 2017, at 3:11 PM, David Hart via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello,<br class=""><br class="">Since the release of Swift 3, I’ve seen quite a few people (me included) experience a lot of friction with the new types for representing ranges. I’ve seen people confused when writing an API that takes a Range as argument but then can’t pass in a ClosedRange. Sometimes this can be fixed because the API should be written against a more general protocol, but sometimes that’s not the case.<br class=""><br class="">Those new types definitely seem to cause more problems than they fixed (the Int.max problem). Has the Standard Library team put any thought into this?<br class=""><br class="">Regards,<br class="">David.<br class="">_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></div></blockquote></div><br class=""></div></body></html>