> On 01 Mar 2015, at 13:33, AlexanderBrenchev via Pharo-dev
> <[email protected]> wrote:
>
>
> Date: 1 Mar 2015 13:24:58 CET
> From: AlexanderBrenchev <[email protected]>
> To: [email protected]
> Subject: New Pharo Collections: Question about MultiDictionary
>
>
> Greetings to everyone. Recently i started my pre-bachelor's work called "New
> Collections for Pharo". ( introduction to my project
> <http://forum.world.st/New-Pharo-Collections-td4794762.html> )
> I decided to start with the MultiDictionary. There is a very basic prototype
> available on my project page on smalltalkhub
> <http://smalltalkhub.com/#!/~OBrenchev/NewPharoCollections>
>
> You can also read my post
> <http://pillarhub.pharocloud.com/hub/brenchev/duntw01nrp9hkz6a00qmi16c5>
> about this implementation on PillarHub.
>
I took a quick look at the current API and I have one small suggestion: I think
it would make sense to add a message #at:add: (the selector is just an example)
and then use that to implement #add: like so (again, just an example):
add: anAssociation
self
at: anAssociation key
add: anAssociation value
This why users are not required to use associations, which are simply
intermediate objects in many cases. If you have large collections you don’t
want to create those intermediate objects.
Cheers,
Max
> At this point, i need your help, users and developers of Pharo! Feel free to
> make your suggestions about functionality of MultiDictionary that you need.
> Also, I'll really appreciate your suggestions about code style and in
> programming with Pharo in general. Thank you and best wishes.
>
>
>
> --
> View this message in context:
> http://forum.world.st/New-Pharo-Collections-Question-about-MultiDictionary-tp4808660.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>
>
>
