ducasse wrote > in Pharo we should write > aCol do: [ :each | each store ]
I always enjoyed the Symbol/Block polymorphism because I thought it was such a clever and visible example of the power of Smalltalk, and, let's face it, I'm lazy and enjoyed saving a few key strokes! That said, I had no idea that there was a dramatic performance cost. Also, the issues you raise about analysis seem important. Since people are free to still use it in their own projects, it doesn't seem to controversial. Can/should we add a lint rule? Can/should it be scoped to Pharo core? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html