Containers and strictness
ekmett at gmail.com
Thu Jun 24 07:59:35 EDT 2010
2010/6/24 Milan Straka <fox at ucw.cz>
> > On 24 June 2010 11:14, Milan Straka <fox at ucw.cz> wrote:
> > > I need some opinion:
> > >
> > > - Do you think methods like insert/lookup/delete/etc should be strict
> > > key/element?
> > >
> > > As Claus wrote, right now it is undocumented and inconsistent (both in
> > > the methods of one container and also in the same methods of different
> > > container).
> > Just as it is sometimes important to be able to do strict inserts, it
> > is important sometimes that we have maps that are lazy in the
> > elements. There are important use cases both ways.
> > So yes we should have some kind of consistent convention. We could do
> > worse than the naming convention where the strict versions use a
> > trailing prime ' character.
> I thought we are talking only about keys/elements. I would leave the
> values untouched.
> Personally I vote for:
> - keys in Maps and elements in Sets are strict
> - vales in Maps are left untouched (lazy)
+1 from me
Great work so far.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libraries