Yeah I was fairly sure that was the direction it should go. Was trying to understand what existed and why. I was also bucketing things in a nondestructive way in the short term until I understood more about the existing Collection code.<br><br>Do we want a ForewardCollection like the prototype or just refocus Collection on that with the two new subprotocols adding in the other behaviors (existing Collection is mostly forward indexing with where on Index type to adjust behavior).<br><div class="gmail_quote"><div dir="ltr">On Sun, Feb 21, 2016 at 4:26 PM Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com">gribozavr@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, Feb 21, 2016 at 4:21 PM, Shawn Erickson <<a href="mailto:shawnce@gmail.com" target="_blank">shawnce@gmail.com</a>> wrote:<br>
> As an FYI I have been playing around with things mostly to get my head<br>
> around the base changes and implications on the existing stdlib<br>
> implementation. It is very early still. I have no issues throwing it away if<br>
> I am way off the rails.<br>
<br>
Thank you! I took a look briefly, and I have a question -- why are<br>
you using ~Indexable as the base protocol? Indexable itself only<br>
exists to work around a compiler limitation and implement<br>
IndexingIterator. Otherwise we should be using Collection.<br>
<br>
Dmitri<br>
<br>
--<br>
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if<br>
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>>*/<br>
</blockquote></div>