-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Consider renaming .connect()
to .join()
#24645
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
Comments
/cc @aturon |
+1, we should do it in 1.1-nighty |
Interesting! I'd always found the It'd be good for this to go through an RFC. We can't do an outright renaming at this point, but we could deprecate the old name and introduce a new one if there's strong enough consensus. (The fact that the methods of this trait are already stable reflects a commitment to the existing names; the lack of stability of the trait is more about how we provide these impls in |
rust-lang/rfcs#1102 merged, this can probably be closed? |
Indeed! |
SliceConcatExt
has a method named.connect()
, which is similar to.join()
in other languages. I don't have any specific numbers, but "join" seems to be used more widely.We could not use "join" because it was previously a keyword. Now it isn't, and
SliceConcatExt
is currently marked as unstable, so how about renaming the method to a more popular name?One blocker is that
SliceConcatExt
is already exported to the prelude. So, although it is technically unstable, the change will still break the currently accepted beta-compatible code.Will this require a RFC?
cc http://www.reddit.com/r/rust/comments/336rj3/whats_the_best_way_to_join_strings_with_a_space/
The text was updated successfully, but these errors were encountered: