-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
make core::str::next_code_point work on arbitrary iterator #33896
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @aturon (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
These are in theory internal only functions that are only exported as an implementation detail between libcore/libcollections, but does this change mean that you're thinking of using them externally? |
I was considering to use |
This seems fine to me -- thanks for the PR! @bors: r+ |
📌 Commit db84fc1 has been approved by |
⌛ Testing commit db84fc1 with merge d1c1a4c... |
💔 Test failed - auto-linux-64-cross-armhf |
@bors: retry On Tue, May 31, 2016 at 3:42 PM, bors notifications@github.com wrote:
|
make core::str::next_code_point work on arbitrary iterator
No description provided.