Re: [math] no-such-integer value

2010-01-14 Thread Isabel Drost
On Mon Grant Ingersoll wrote: > I'm sensing a theme. I think for this stuff we should prune fairly > aggressively, then add back in places once we have a need. +1 Isabel

Re: [math] no-such-integer value

2010-01-11 Thread Grant Ingersoll
I'm sensing a theme. I think for this stuff we should prune fairly aggressively, then add back in places once we have a need. On Jan 10, 2010, at 11:51 PM, Jake Mannix wrote: > On Sun, Jan 10, 2010 at 8:05 PM, Ted Dunning wrote: > >> Nuke it if you don't use it. >> > > +1 to this > > -jak

Re: [math] no-such-integer value

2010-01-10 Thread Jake Mannix
On Sun, Jan 10, 2010 at 8:05 PM, Ted Dunning wrote: > Nuke it if you don't use it. > +1 to this -jake

Re: [math] no-such-integer value

2010-01-10 Thread Ted Dunning
Nuke it if you don't use it. On Sun, Jan 10, 2010 at 7:36 PM, Benson Margulies wrote: > Personally, I'd be inclined to nuke the entire API. It's implemented > as the obvious iteration, and the caller can iterate for themselves > without creating a shoot-yourself opportunity for the unwary. > > An

[math] no-such-integer value

2010-01-10 Thread Benson Margulies
Colt code is inconsistent in dealing with the following case: iIntSomethingHashMap.keyOf(someValue) Some code we got from them returns 0 if there is no such value, other code returns MIN_VALUE. In floating-point land, it returns NAN. Personally, I'd be inclined to nuke the entire API. It's impl