Thread overview | ||||||
---|---|---|---|---|---|---|
|
February 20, 2021 [Issue 21650] parse form that returns elements parsed is too difficult to use | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=21650 --- Comment #1 from adela.vais99@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 -- |
February 21, 2021 [Issue 21650] parse form that returns elements parsed is too difficult to use | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=21650 --- Comment #2 from Steven Schveighoffer <schveiguy@gmail.com> --- 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. -- |
December 17, 2022 [Issue 21650] parse form that returns elements parsed is too difficult to use | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=21650 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P4 -- |
December 01 [Issue 21650] parse form that returns elements parsed is too difficult to use | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=21650 --- Comment #3 from dlangBugzillaToGithub <robert.schadek@posteo.de> --- THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/phobos/issues/10457 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB -- |
Copyright © 1999-2021 by the D Language Foundation