[Pharo-dev] Missing collectAsSet: in Pharo 3.0

Benjamin Benjamin.VanRyseghem.Pharo at gmail.com
Tue Dec 10 08:40:16 EST 2013


Being consistent does not mean we have to be absolute :)

Ben

On 10 Dec 2013, at 14:38, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> wrote:

> And then rejectAsSet: selectAsHeap: etc...
> A big -1
> 
> 
> 2013/12/10 Yuriy Tymchuk <yuriy.tymchuk at me.com>
> 
> On 10 Dec 2013, at 14:26, Roberto Minelli <roberto.minelli at usi.ch> wrote:
> 
> > No. Since #flatCollectAsSet: is in the image, #collectAsSet: should be in the image as well.
> >
> > And then, since we want clean code #collectAsSet: is cleaner than #collect:as:.
> 
> Yes, but this also means that you need to implement:
> 
> collectAsArray:
> collectAsOrderedCollection:
> collectAsBag:
>> 
> :)
> 
> >
> > On Dec 10, 2013, at 2:23 PM, Esteban Lorenzano <estebanlm at gmail.com> wrote:
> >
> >> I don't think it has to be in the image,
> >>
> >> After all, you can just replace your calls for #collect:as:
> >>
> >> Esteban
> >>
> >>
> >>
> >>
> >> On Tue, Dec 10, 2013 at 2:21 PM, Roberto Minelli <roberto.minelli at usi.ch> wrote:
> >> Hi,
> >>
> >> In Pharo 3 you guys integrated Doru’s CollectionsExtension package, which is great.
> >>
> >> You forgot, however, to integrate the utility method #collectAsSet: I was using in several places in my code.
> >>
> >> It should be simply
> >> ^ self collect: aBlock as: Set
> >>
> >> Could someone please put this in the standard image please? Thanks.
> >>
> >> Cheers,
> >> R
> >>
> >
> >
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131210/aae75dc9/attachment-0002.html>


More information about the Pharo-dev mailing list