You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current situation is not quite consistent w.r.t. parseJSONStream here, but parseJSONValue follows std.conv:
parseJSONValue takes a reference to an input range and consumes a single JSON value, leaving the rest of the range intact
toJSONValue takes an input range by value and expects it to contain exactly one JSON value
Taking this as the basis, parseJSONStream would actually have to be renamed to toJSONStream, but since it parses lazily that doesn't seem to capture the meaning very well.
Yes and no. No, because the semantics are also different between the two: to throws if there is more in the input than a single value (modulo whitespace), while parse just leaves any excessive contents in the input.
The following fails to compile:
And so does the following:
The text was updated successfully, but these errors were encountered: