You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
I haven't mimicked the GroupBy method exactly, there's 1 overload that isn't implemented, and that's the one that takes in the key & result selector. This is because the only distinguishing property between a lambda that selects the element to use and the one that creates the result element is that the former has 1 parameter, and the second 2.
Having the groupBy function do different behaviour on this factor alone feels like it is very much open to weird behaviour if someone puts in a function with an unexpected number of arguments, so I have not done it. Instead, you should do:
The only difference to the Linq method is that you explicitly pass e => e instead of it being implicit, which I think is better for the library (since the explicit behaviour difference is clearer overall).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
i have never fully understood group-by, even in SQL, so i'll need to get on that an implement these methods
The text was updated successfully, but these errors were encountered: