Skip to content
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

fix(3245): fix R.dropLast with negative and zero param when used as transducer #3246

Merged
merged 1 commit into from
Mar 6, 2022

Conversation

xgbuils
Copy link
Contributor

@xgbuils xgbuils commented Feb 26, 2022

It fixes #3245

@xgbuils xgbuils changed the title fix(3245): fix R.dropLasr with negative and zero param when used as transducer fix(3245): fix R.dropLast with negative and zero param when used as transducer Feb 26, 2022
@CrossEye
Copy link
Member

CrossEye commented Mar 6, 2022

I really hate supporting negative indices in general, but we should be consistent in it.

🌿

@CrossEye CrossEye merged commit cd47cbd into ramda:master Mar 6, 2022
@adispring adispring mentioned this pull request Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wrong behaviour in R.dropLast(0/negative) when used as transducer
3 participants