encoding/csv: LazyQuotes option breaks if the fields are unquoted and the lazy quotes appear at the beginnng of the field

[gopherbot]

by [email protected]:

Similar to issue #6258, but not the same.

What steps will reproduce the problem?
Try to read a CSV file where the fields are unquoted and one of them begins in something
that would need lazy quotes, e.g.
Field1,Field2,"LazyQuotes" Field3,Field4,Field5

What is the expected output?
["Field1", "Field2", "\"LazyQuotes\" Field3",
"Field4", "Field5"]
Length 5

What do you see instead?
["Field1", "Field2", "LazyQuotes\"
Field3,Field4,Field5"]
Length 3

Which compiler are you using (5g, 6g, 8g, gccgo)?
Whatever the default is from https://code.google.com/p/go/downloads/list

Which operating system are you using?
Mac OS X 10.8

Which version are you using?  (run 'go version')
go version go1.1.2 darwin/amd64

[robpike]

Comment 1:

Issue #6286 has been merged into this issue.

[robpike]

Comment 2:

Issue #6285 has been merged into this issue.

[robpike]

Comment 3:

Issue #6284 has been merged into this issue.

[gopherbot]

Comment 4 by [email protected]:

Ah, sorry about there being a lot of these - I kept getting 502 errors when I was trying
to post them so assumed that it had not posted successfully...

[gopherbot]

Comment 5 by [email protected]:

I think something like this would be impossible to handle correctly if you didn't have
the context to know that the fields are supposed to be unquoted...

[robpike]

Comment 6:

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

[rsc]

Comment 7:

Labels changed: added go1.3maybe.

[rsc]

Comment 8:

Labels changed: added release-none, removed go1.3maybe.

[rsc]

Comment 9:

Labels changed: added repo-main.

[dsnet]

I believe this is working as intended. A quote at the beginning signifies that this is a quoted string, and the parser continues to follow the appropriate lazy rules for quoted strings.