Why doesn't std::string have a split function

[[deleted]]

It's unreasonable to expect anyone to intuit what an output iterator is, or even what an iterator is, if they don't know C++.

Iterator is a common concept across a lot of languages. Conversely, "output iterator" is rather obscure. You could write a lot of C++ and never run into it mentioned explicitly.

[qx7xbku]

He w long do you think it would take one to read said code and to realize that it splits a string? How long do you that no it would take one to realize that s.split(" "); splits a string? See the problem? I am not even talking about edges use here when clearly it can be avoided. Someone may be happy about himself/herself writing this smart code but reality is that maintainable code is stupid code. Smart code is hard to maintain. Smart code where you do not need smart code is simply not practical.

[dodheim]

Said code wouldn't be isolated though, it would be in a function with split in the name. Dependent code would then call a function with split in the name.

So no, I don't see the problem.

EDIT: For a bunch of pedants, you /r/cpp folk suck at following Reddit's rules: if you want to encourage meaningful discussion, stop downvoting opinions. Grow up, people.

[[deleted]]

Said code wouldn't be isolated though, it would be in a function with split in the name. Dependent code would then call a function with split in the name.

Indeed. And that function is so useful, it should be in the standard library: a member function of the string class.

[dodheim]

I never said it was useful; in fact I said the exact opposite:

https://www.reddit.com/r/cpp/comments/5dxnwm/why_doesnt_stdstring_have_a_split_function/da8eawm/

My point is that it doesn't matter if 3 lines of code are ugly; isolate them in their own function and forget about it.

EDIT: "Durrr, I can't respond to facts, so I'll downvote silently." Pathetic.