[Issue 21650] parse form that returns elements parsed is too difficult to use

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21650

Iain Buclaw  changed:

   What|Removed |Added

   Priority|P1  |P4

--


[Issue 21650] parse form that returns elements parsed is too difficult to use

2021-02-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21650

--- Comment #2 from Steven Schveighoffer  ---
I don't think having both overloads would break any code. Types don't match
values, values don't match types.

parse(Target, Source, Flag!"doCount" doCount)(Source rng) will match existing
uses that specify the source range type explicitly

parse(Target, Flag!"doCount" doCount, Source)(Source rng) will match new uses
that want to use IFTI to detect the Source range type.

What was discussed in that thread is inserting the flag in *existing*
functions. I'm talking about adding overloads to address the new usage.

--


[Issue 21650] parse form that returns elements parsed is too difficult to use

2021-02-20 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21650

--- Comment #1 from adela.vai...@gmail.com ---
The order you suggested would have introduced breaking changes. See a thread
here [1].

[1] https://github.com/dlang/phobos/pull/7642#discussion_r493478675

--