I don't anticipate any big problems in making the default value configurable.
Yes, Trove has the complete cross-product, so matching that sure makes
a code generator attractive.
On Wed, Dec 16, 2009 at 6:18 PM, Ted Dunning wrote:
> This seems most congenial. As Jake says, 0 is definitely handi
This seems most congenial. As Jake says, 0 is definitely handier for the
sparse matrix/vector case and NaN is very nice for the collection case.
On Wed, Dec 16, 2009 at 3:10 PM, Jake Mannix wrote:
> Of course, you could also just have the {X}{Y}Map take a default value in
> the constructor, and
On Tue, Dec 15, 2009 at 5:26 AM, Benson Margulies wrote:
> As to float and double, they may need to be special cases. Ask
> yourself: "What should get(k) return when containsKey(k) is false and
> the payload is double?"
>
> Answer 1: NaN.
> Answer 2: zero, like with the int types.
>
I actually fe
I have half of an SGD logistic regression written. There might be some code
to share. I will put up a patch shortly so that others can follow progress.
There is also a group of four (very quiet) developers who are working on
something related to SVM. I will be meeting with them tomorrow morning
