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
It's not obvious to me what the correct behavior is, but someone was hacking abusing CSV to act a trivial parser to read a file as a slice of newline seperated items.
The text was updated successfully, but these errors were encountered:
dsnet
changed the title
encoding/csv: regression
encoding/csv: regression in handling of
Oct 23, 2017
dsnet
changed the title
encoding/csv: regression in handling of
encoding/csv: regression in handling of '\n' delimiters
Oct 23, 2017
dsnet
added
the
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
label
Oct 23, 2017
Change https://golang.org/cl/72793 mentions this issue: encoding/csv: forbid certain Comma and Comment runes
dsnet
added
NeedsFix
The path to resolution is known, but the work has not been done.
and removed
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
labels
Oct 25, 2017
Consider the following:
Prior to CL 72150, this would print:
On tip, it prints:
It's not obvious to me what the correct behavior is, but someone was
hackingabusing CSV to act a trivial parser to read a file as a slice of newline seperated items.The text was updated successfully, but these errors were encountered: