-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add simple values() method in Tensorics to retrieve all the values of a Tensor #42
Comments
Hi @delph74 What would you expect as a return type of such a method? |
Hello @kaifox , |
As far I remember, a tensor has no 'values' like method. But (if implements Mappable, and this is the case for the ImmutableTensor) it has The practical use of such values collection (only values) may be very limited, as this may vary with their position in the Tensor (coordinate). |
yes, then its clear! Potentially uniqueValuesOf(...) as the other methods in Tensorics? public static final <T> Set<T> Tensorics.uniqueValuesOf(Tensor<T> tensor); In general, I clients should void using also the asMap() method directly ... In general, Tensorics.mapFrom(Tensor t) should be used. This calls asMap() if available, which makes it more efficient.... |
Hey @agorzawski !!! Cool to see you here! |
@kaifox I just want to recall, that I have never left this project ;-) |
Yes @kaifox , something like that would be perfect. |
Maybe one more thing - there is |
yes of course it it possible and not to difficult to get all the values of a Tensor, like that for example So nothing urgent or really missing, just for convenience and make it easier. |
Good point @michi42 ! ... Still, convenience methods can still be justified... I think there is nothing against adding it. |
@agorzawski , good to hear! |
Yes sure, I did not mean to object that :-) |
I know ;-) |
Just wanted to encourage @delph74 to add it if she feels like ;-) |
Yes why not, I would then add my first contribution to tensoric project ✌️ 😃 |
Cooool!!!!! |
No description provided.
The text was updated successfully, but these errors were encountered: