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
I noticed that the parse errors contain neither line numbers nor column numbers (assigning a decoding error to a column).
The first can be easily circumvented by parsing the file line-by-line, and keeping track of which line we are in.
The second is baked into sv, due to the fact how it accumulates errors into a Semigroup of DecodeError;
I think column errors could be added by putting them into BadParse, however they only really make sense if you are parsing line-by-line; however, if you are not doing that, the resulting errors will be pretty useless anyway, because there won’t be any underlying position for BadParses, and you just get a structureless list. I feel like this is a architectural problem with sv though.
The text was updated successfully, but these errors were encountered:
I noticed that the parse errors contain neither line numbers nor column numbers (assigning a decoding error to a column).
The first can be easily circumvented by parsing the file line-by-line, and keeping track of which line we are in.
The second is baked into
sv
, due to the fact how it accumulates errors into aSemigroup
ofDecodeError
;I think column errors could be added by putting them into
BadParse
, however they only really make sense if you are parsing line-by-line; however, if you are not doing that, the resulting errors will be pretty useless anyway, because there won’t be any underlying position forBadParses
, and you just get a structureless list. I feel like this is a architectural problem withsv
though.The text was updated successfully, but these errors were encountered: