<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><br>On 30 Jan 2016, at 02:47, Alex Migicovsky via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><div class="">IMO the ‘like’ suffix makes it sound like the conforming type to Collectionlike is <i class="">like </i>a Collection, but not exactly a Collection. </div></div></blockquote><div><br></div><div>and isn't this the point of protocols? To decouple the behaviour you expose/the contract you make from what you actually are/how you are implemented?</div><br><blockquote type="cite"><div><div class="">Maybe there’s another suffix that works but I don’t think this one conveys the right information.</div><div class=""><br class=""></div>- Alex<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 29, 2016, at 6:43 PM, Brent Royal-Gordon 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=""><blockquote type="cite" class="">Count me among those who liked the ‘Type’ suffix for protocols though.<br class=""></blockquote><br class="">I wonder if we can't change it to a -`like` suffix. Applying that to 2.1 stdlib gives you:<br class=""><br class="">AnyCollectionlike<br class="">BidirectionalIndexlike<br class="">BitwiseOperationslike<br class="">Booleanlike<br class="">CVarArglike<br class="">Collectionlike<br class="">Errorlike<br class="">FloatingPointlike<br class="">ForwardIndexlike<br class="">Generatorlike<br class="">IntegerArithmeticlike<br class="">Integerlike<br class="">Intervallike<br class="">LazyCollectionlike<br class="">LazySequencelike<br class="">MirrorPathlike<br class="">MutableCollectionlike<br class="">OptionSetlike<br class="">OutputStreamlike<br class="">RandomAccessIndexlike<br class="">RangeReplaceableCollectionlike<br class="">ReverseIndexlike<br class="">Sequencelike<br class="">SetAlgebralike<br class="">SignedIntegerlike<br class="">SignedNumberlike<br class="">UnicodeCodeclike<br class="">UnsignedIntegerlike<br class=""><br class="">Not all of these are perfect, but in some cases that's because they should arguably be -able protocols (BitwiseOperationsType -> BitwiseOperable).<br class=""><br class="">-- <br class="">Brent Royal-Gordon<br class="">Architechies<br class=""><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=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></div></blockquote></div><br class=""></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>