New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

benchmark: compare the performance trade-offs of validating each `.csv` row on read, vs. validating only the final constructed `.csv` #24

Open

jdhoffa opened this issue Feb 27, 2025 · 0 comments

Assignees

Collaborator

jdhoffa commented Feb 27, 2025

          I'm happy to merge this as-is, but it would be interesting to see what the performance trade-offs are with validating each row on read.

Something to look into in the future

Originally posted by @jdhoffa in #23 (comment)

The text was updated successfully, but these errors were encountered:

jdhoffa self-assigned this

jdhoffa changed the title ~~test: compare the performance trade-offs of validating each .csv row on read, vs. validating only the final constructed .csv~~ benchmark: compare the performance trade-offs of validating each .csv row on read, vs. validating only the final constructed .csv

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment