Ehance ddoc for std.array.split.

[mdparker]

This started with fixing a simple typo, but I decided to go ahead and go all out. If I'm on the right track with this, I'll do more.

I've added an extra paragraph, appropriate DDOC tags (Examples, Params, Returns), and changed the template type parameters to match the type parameters for std.algorithm.splitter. I also renamed the delimiter parameter to 'sep' to match std.array.join which follows this (std.algorthim.splitter calls it 's' instead).

I'm not sure about the description of the returned array. Should it be called an 'array of ranges'?

Finally, I think the version of the template that has the 'alias isTerminator' needs to be documented separately, but I haven't figured out yet what that template alias is doing.

[JakobOvrum]

Function, not operator

[mdparker]

That was in the original text and I overlooked it. Updated.

[ghost]

Can we avoid using single characters for the range? It's even easier to read the docs if we use range as the parameter name.

[ghost]

Or use rng if we're saving characters, not sure..

[mdparker]

Changing 'r' to 'range' is fine with me. We ought to be consistent about it, though, since 'r' is used in a lot of places.

[ghost]

Could you squash the first two commits together? (the ones introducing and then changing operator->function)

[mdparker]

Sure, if you give me some hints on how to do it.

[mdparker]

Oh, nevermind. I see "squash" is a real thing. I'll figure this out.

[ghost]

Ah sorry, I haven't realized you're new to Git!

Typically you would use the git interactive mode to edit the commits. For example:

# edit the last two commits
$ git rebase -i HEAD~2

And then you usually get a vi editor (or notepad probably on Windows) with:

pick <sha> Ehance ddoc for std.array.split.
pick <sha> Minor edit of the See_Also.

You can change the second pick to either s (squash) or f (fixup). The terminology is a little loose, typically we say squash when we really mean fixup. The only difference between the two is: When using squash, you'll get a new commit message that is a combination of the two commit messages. You can still edit that message entirely, of course.

In your case you can simply use a fixup.

[mdparker]

So after googling how to squash and how to move around the editor in git-bash (which appears to be vim), I think I've managed it somehow.

[mdparker]

I've been happily using git for a few years now. Just pushing and pulling for the most part. This is my second PR ever.

[ghost]

Good job! Done it without my help. :P

[ghost]

Auto-merge toggled on

[yebblies]

Auto-merge toggled on

This will work a lot better now that I've approved him on the autotester.

[ghost]

This will work a lot better now that I've approved him on the autotester.

lol! I didn't see the status anywhere so I just replace the typical autotester URL with /2817 and it worked.

Perhaps there should be a message here in the status bar "Author not approved for auto-testing" or something. :)