-
Notifications
You must be signed in to change notification settings - Fork 675
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
Implement copy_file_range() #1069
Conversation
You'll need to rebase and fix the CHANGELOG entry. Also, please wrap everything to 80 columns. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I said "wrap everything to 80 columns" I meant to only wrap new code, not existing code. Now you have a big change that mixes style with content. That's not good. Please undo it. If you want to wrap the rest of the file, that should be done as a separate commit.
This should be fine, right? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It all LGTM now, but you need to rebase to fix the CHANGELOG.
I have rebased and fixed the changelog. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bors r+
Build succeeded
|
@asomers It seems that I made a mistake in this PR: The function should be in |
Honestly I wouldn't bother. The user disruption that would come by renaming the symbol isn't worth the gain to consistency. |
Why not export it in the correct place, and re-export it in |
This should fix the problems with #971 and #1008.