> On 21 Jan 2020, at 23:56, Sven Van Caekenberghe <[email protected]> wrote:
>
> I also like the use of symbols but more for casual code.
>
> I know using blocks can be faster, but the difference is not massive.
The difference is not only in speed.
And it is exactly why I do not like value in Object.
> What I don't understand is why it is so super bad. Polymorphism will always
> be there, that is really powerful, when used wisely. I can't immediately see
> why one or the other would make analysis easier or better. Can you explain ?
See my reply to esteban.
>> On 21 Jan 2020, at 23:37, Sean P. DeNigris <[email protected]> wrote:
>>
>> 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
>>
>
>
