<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 2, 2017, at 9:46 PM, Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Jan 31, 2017, at 11:16 AM, Ben Cohen via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><blockquote type="cite" class=""><br class="">As we expand (and maybe contract :) the standard library, this kind of question comes up a lot, so it is worth setting out some criteria for judging these “helper” methods. Here’s my take on such a list (warning: objectivity and subjectivity blended together in the below).<br class=""></blockquote><br class="">This is great perspective Ben, thank you for taking time to write this up!<br class=""><br class="">It seems that you are leaning towards removing enumerated(). What do you think about the proposal of removing enumerated but adding indexed() to replace it? It would provide the same behavior for common array cases, while providing more useful/defensible functionality for other collections.<br class=""><br class="">-Chris<br class=""></div></div></blockquote><br class=""></div><div><a href="https://gist.github.com/erica/2b2d92e6db787d001c689d3e37a7c3f2" class="">https://gist.github.com/erica/2b2d92e6db787d001c689d3e37a7c3f2</a></div><div><br class=""></div><div>This could easily be adapted to incorporate both the removal of enumerated as well as the addition of indexed, and I love the idea of using Ben's list as a template for the justification section, plus adding the feedback from this thread.</div><div><br class=""></div><div>-- E</div><div><br class=""></div><br class=""></body></html>