Uh oh!
There was an error while loading. Please reload this page.
make core::str::next_code_point work on arbitrary iterator - #33896
Conversation
rust-highfive
commented
May 27, 2016
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. |
alexcrichton
commented
May 27, 2016
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? |
strake
commented
May 27, 2016
I was considering to use |
aturon
commented
May 31, 2016
This seems fine to me -- thanks for the PR! @bors: r+ |
bors
commented
May 31, 2016
📌 Commit db84fc1 has been approved by |
bors
commented
May 31, 2016
⌛ Testing commit db84fc1 with merge d1c1a4c... |
bors
commented
May 31, 2016
💔 Test failed - auto-linux-64-cross-armhf |
alexcrichton
commented
May 31, 2016
@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.