Scott Sauyet

Thanks, as always!

@Andarist: > I'm not a project maintainer here... Would you like to be one? You've made invaluable contributions for quite some time. I'd have to check with the other maintainers,...

I can tell you briefly that this certainly has to do with cycle-detection. It's pretty hard to pretty-print something like this: ```js const x = {} x.x = x toString(x)...

I'm thinking that instead of using the internal `_includes` -- which then calls `equals` -- for testing circularity, we should instead just test reference equality. I think that makes sense,...

@customcommander: Yes, that was the point of `toString`. The fact that we dispatch to `equals` is simply a side-effect of the implementation details. We can certainly work around this.

I can't think of any issues. I think it won't be too difficult to change.

Thank your for the PR. I'm afraid I forgot to do the research into why `uncurryN` doesn't already handle this. I will try to do so soon. Did you look...

This does seem far less than ideal. Do you have a recommendation? Note that `g(1)(_, 2, _, 'a')` is a simpler demonstration.

In keeping with other Ramda functions, I would like to pass along extra arguments if they're supplied. So `g(1)(_, 3)(2, 'a')` should yield `f(1, 2, 3, 'a')`, even though `f`...

Whatever we do here, we should also make sure we account for in `equals`.