-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Transducers: map(prop(p)) != pluck(p) ? #1012
Comments
Doing a quick and dirty, and replacing R.pluck with tpluck in the above snippet, I also get the expected [2, 3]. function tpluck(prop) {
return R.map(function(x) {return x[prop];});
} |
The problem, of course, is that If I'm not mistaken, and I can't tell for sure until I get in front of a computer, it's because |
Probably it's not the underlying cause of the issue, but I noticed that ramda transducers don't follow the old or the new transducers protocol (https://github.com/cognitect-labs/transducers-js#the-transducer-protocol) which I ran into the hard way. Using Kefir.js for 'FRP', I failed to switch from transducers.js / transducers-js to ramda in a test. Is it due to some fundamental difference in the implementation approach? |
make pluck behave with transducers, fixes #1012
Interesting, I was already up to date and Kefir still balked at a point which I could solve by switching a R.map inside a R.compose to a t.map (transducers.js). |
please keep me posted -- i am interested to know what places we missed and need to bring into compliance. thanks |
I must be overlooking something obvious:
With full application:
So far, so good. Now with transducers:
It is still good, however this won't work:
The text was updated successfully, but these errors were encountered: