benchmark: make output RFC 4180 compliant#37038
Closed
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I had trouble importing the generated CSV into other software because it doesn't conform to RFC 4180, the de facto standard for CSV.
Relevant information from the RFC:
Since spaces are considered part of a field, we end up with fields of the form
' "foo"'(note the space in front of the quoted value), and now the quote isn't the first character within the field, so it violates the RFC.