liquidaty

OK, appears to have been the result of some other merge that took place after the last time this PR was modified, resulting in git not knowing how to merge...

@pkoppstein think this bad boy is good to go now

@pkoppstein yes, apologies for not squashing, for this last flurry of changes, in some cases (like the manual.yml commit) I should have been more thorough in running the local tests...

@malespiaut just added pull parsing API, which if I'm guessing correct, you'll appreciate. No need for callbacks: ``` zsv_parser parser = zsv_new(...); while(zsv_next_row(parser) == zsv_status_row) { /* for each row...

I implemented this in a different body of code than simd-everywhere but here is the code I used. Note, this basically is exactly what @aqrit suggested and it seems to...

I'll add one I maintain: https://github.com/liquidaty/zsv I'm sure with the intellectual firepower on this repo, you can beat zsv, or perhaps someone already has, but I haven't yet seen that,...

OK. Using this approach, how would the ci.yml script assign a value to TAG, if it isn't hardcoded?

Thanks for the thoughtful response. > I'd want to understand what needs to be optimized in this case before throwing in more keywords. Just to clarify, my suggestion would not...

BTW zsv hits all of the Tools categories listed in this repo: * [Repair or Validate CSV](https://github.com/secretGeek/AwesomeCSV#repair-or-validate-csv): YES * [Treat CSV as SQL](https://github.com/secretGeek/AwesomeCSV#treat-csv-as-sql): YES * [Convert to or from CSV](https://github.com/secretGeek/AwesomeCSV#convert-to-or-from-csv):...

Is this something that could easily be added as a makefile optional target that would install command completion when run?