std.conv.parse not accepting ByCodeUnitImpl

[Steven Schveighoffer via Digitalmars-d-learn]

On 5/25/16 12:10 PM, Jack Stouffer wrote:
> On Wednesday, 25 May 2016 at 15:34:45 UTC, Steven Schveighoffer wrote:
>> parse consumes data from the string as it goes.
>
> I know that, I'm asking why. This disallows the natural range chaining
> and forces you to save to a variable before calling parse even though
> the function works just as well without it.

If parse returned the leftover string, and took the data to parse as the 
ref parameter, then it doesn't fit into other use cases.

>> If you want to leave the data there, use to instead.
>
> Can't without calling std.array.array.

Is there a specific use case that doesn't work? to should work wherever 
parse works (in fact, whenever you call to!someType(someString), I 
believe it just forwards to parse).

-Steve