-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Added examples/docs to split in str.rs #33893
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @gankro (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. |
Looks great! If you say "Fixes #33882" in your commit message, it will close the issue when this gets merged. Would you mind amending the message to put this in? |
Absolutely, just fixed that. Thanks for the heads up! On Thu, May 26, 2016 at 6:57 PM, Steve Klabnik notifications@github.com
|
I am not seeing the fix, did you push it? Also, Travis seems to be failing. My internet connection is terrible, so it's not showing me why, but that has to be passing before we can merge too 😄 |
I'm seeing the command "make tidy && make check-notidy -j4" exited with 2." On Thu, May 26, 2016 at 7:31 PM, Steve Klabnik notifications@github.com
|
Trailing white space was the issue. I fixed the offending lines. |
I don't think we should commit to this weird behavior, we should probably copy some other language's standard library here. |
Please squash your commits. |
Rebase doesn't seem to be doing the trick. Am I squashing incorrectly? (git newbie here) |
@Ophirr33 I wrote a blog post that might be helpful: http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request |
Added documentation clarifying the behavior of split when used with the empty string and contiguous separators.
Got it! Thanks again |
@bors: r+ rollup |
📌 Commit feb0b27 has been approved by |
⌛ Testing commit feb0b27 with merge 69da70d... |
💔 Test failed - auto-linux-64-opt-rustbuild |
@bors: r+ rollup |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit feb0b27 has been approved by |
…uillaumeGomez Added examples/docs to split in str.rs Added documentation clarifying the behavior of split when used with the empty string and contiguous separators. Addresses issue [33882](rust-lang#33882). This is my first time contributing to rust, so forgive me if I'm skipping any of the contribution steps. Fixes rust-lang#33882
…uillaumeGomez Added examples/docs to split in str.rs Added documentation clarifying the behavior of split when used with the empty string and contiguous separators. Addresses issue [33882](rust-lang#33882). This is my first time contributing to rust, so forgive me if I'm skipping any of the contribution steps. Fixes rust-lang#33882
Maybe it is the wanted behavior. With the current results, |
@bors: retry |
…uillaumeGomez Added examples/docs to split in str.rs Added documentation clarifying the behavior of split when used with the empty string and contiguous separators. Addresses issue [33882](rust-lang#33882). This is my first time contributing to rust, so forgive me if I'm skipping any of the contribution steps. Fixes rust-lang#33882
Added documentation clarifying the behavior of split when used with the empty string and contiguous separators. Addresses issue 33882. This is my first time contributing to rust, so forgive me if I'm skipping any of the contribution steps.
Fixes #33882