Support the case where no user-specified delimiter is needed

[laicasaane]

There is a behavior of the standard string.Split where it accepts an empty array of delimiter and assumes that we want to use white-space characters.

From the Remarks section of String.Split:

If the separator parameter is null or contains no characters, white-space characters are assumed to be the delimiters. White-space characters are defined by the Unicode standard and the Char.IsWhiteSpace method returns true if they are passed to it.

It is convenient to also have this behavior in the multi-lingual context where we don't have to maintain a complete list of white-space characters on our own.

[dragon7307]

Yeah, thanks for spotting this.

So neither the legacy Split methods, nor our backward-compatible defaults to the .Net Split methods exhibit this behaviour, thus technically making this issue a bug and not an enhancement, since functionality differs acrross .Net (Core) Versions.

I, need to roll out Net 10 support either way, so I'll be including this in the next update, expect this to take a coupl,e weeks though, since I am taking some vacation the coming weeks.

[laicasaane]

I, need to roll out Net 10 support either way

Will the library maintain compatibility to .NET Standard 2.1? I need to use it within Unity though.

[dragon7307]

Yes, any currently supported version will stay supported for the forseeable future, including .Net Standard 2.1.
Compatibility with new versions is solely added, since dotnet is catching up with span-related functionality and some features we already have, must be excluded from newer versions of .Net when they become standard for the saker of avoidng conflicts.
Inversely, we aim to make new developements accessible in many older .Net versions as well.