[Issue 17438] std.conv.parse documentation contradiction

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=17438

Vladimir Panteleev <dlang-bugzilla at thecybershadow.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #4 from Vladimir Panteleev <dlang-bugzilla at thecybershadow.net> ---
The description of the function family, as quoted above, says "It does not
throw if it could not convert the entire input." Personally I don't find that
ambiguous, but I guess we do have a sample size of one of it being
misinterpreted. I find it unambiguous because if you were to interpret it as
"it does not throw", it would mean that 1) the last part of the sentence would
be redundant as well as misleading, and would have no reason to be included; 2)
as pointed out, it would contradict the individual functions' "Throws:"
sections; 3) if the functions were to never throw, what would their return
value be when absolutely no useful information was extracted from the input
text?

Since as far as I can see this issue was filed out of a misinterpretation of
the documentation, and there's been no reply to my last comment in over 24h, I
guess the misunderstanding has been settled; either way, I don't see any
actionable point here right now. If you think that the misunderstanding
occurred due to something lacking in the documentation and can suggest a
concrete improvement to the documentation that would avoid such a
misunderstanding from occurring again, please reopen and/or submit a pull
request.

(In reply to Brad Roberts from comment #2)
> Re-read the description of the parse family of functions I cut and pasted
> into the bug report (which is still what the page says).

Funny how you're telling people to re-read things when the misunderstanding was
on your side. Let's be nice, OK? :)

--