I have no idea how much it would cost too change * to + for string concatenation. That's where you value tools such as clang-modernize on C++ or corresponding tools on Go. Perhaps the best way to get rid of it is to enforce the change.
Maybe allowing + and * for a few iterations, and removing * before 1.0. Then you won't hear about it anymore. Otherwise, people will rightly complain about it for a long time. I guess that the fix itself is trivial (simply remove the method > definition or change its name), but the associated costs may not be > (breaking code), and from the discussion in the issues it looks like the > decision has not been made yet. > > Again, I do think that * and ^ for strings is not an ideal choice, but I > am still surprised how often this issue crops up and how strongly people > feel about these infix ops. Its not like one has to use them, if you > don't like * or ^ for strings, there are `string` and `repeat` and a few > other alternatives which may be more suitable in certain cases. This is > what I do at the moment. > > Perhaps limiting the number of discussion threads about > *(s::AbstractString...) to 1/month would not be a bad idea :P > > Best, > > Tamas >
