-
Notifications
You must be signed in to change notification settings - Fork 94
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
Improve API design for String::concat #1496
Comments
I REALLY dislike |
This proposal makes the syntax even uglier in my opinion. |
here is a possible API design Iter::join(self : Iter[String], separator~ : String = ..) -> String |
Are you seeking this? |
String::concat might need to be deprecated, otherwise, we need add concat_arrayview, concat_deque....., we shouldn't do the same thing in different way |
if we concat Array[String], we have to
xxx.iter().to_array()
, I consider useIter[String]
uniformly handle all sequence.and if Iter[String] is non termination, concat also is non termination, User should use Iter::take, before concat
String::concat
Origin
New
Array::flatten
Origin
New
The text was updated successfully, but these errors were encountered: