Previously on “Collecting Collections”
After gathering a bunch of methods in a table and reading their source or documentation, I had a basic idea for every one of them.I wanted to reduce the amount of necessary concepts to work with a collection. Something like 250 was too much.“Maybe if I make a graph, analyzing which method depends on which other I could get a view of the important ones”. At least that’s what I thought.
15 Nov 2013
Previously on “Collecting Collections”
I was designing in my head, analyzing how to implement each method, visioning dependencies between methods and I stumbled upon size
.
Very simple to implement. Perhaps so simple that two different implementations popped in my head.
15 Nov 2013
Some time ago I started digging collection APIs in a few languages trying to answer a philosophical question. How were the whole/part relationships represented on programming languages (through collections) and what were the operations that we (as programmers) used on them.What started as a few minutes skimming through collections sources in Smalltalk, Java and (thanks to Ignacio) Ruby, have become an intensive and interesting work of exploration and discovery that branched more questions and a toy Java project also.
6 Nov 2013