-
Notifications
You must be signed in to change notification settings - Fork 12
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
Intersect #19
Comments
I suppose we will also need to have something like an We would have an optional value which would specify in which way to do an intersection. Something like this?
Maybe it would also be a good idea to create comparers for simple types(string, number, etc...) which would be automatically used(depending on the type) if no comparer is specified. |
The only place where comparers are being used currently is for We can introduce something like this: export type EqualityComparer<T> = (left: T, right: T) => boolean;
export const StrictEqualityComparer = <T>() => (left: T, right: T) => left === right; |
It all depends how precise you want to go. I'd argue that for strings, as an example, being careful about locale is a must. And |
yep, but in the end, having special comparer for those cases is user's responsibility. |
Since EqualityComparer is there already, I'll grab this task. |
Produces the set intersection of two sequences (deferred execution)
Proposed signature:
The text was updated successfully, but these errors were encountered: