Athan

Hey, @dorrin-sot. Same concern as the other issue. Namely, I need to update the reference implementations. Maybe consider https://github.com/stdlib-js/stdlib/issues/227?

@mhmdaminraeisi You mind checking the box above to indicate that you've read the contributing guidelines? In particular, checking this box means agreeing to the [licensing terms](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md#developers-certificate-of-origin-11).

@mhmdaminraeisi Checking in to see if you'd be willing to update your OP as discussed above.

@mhmdaminraeisi Checking in to see if you'd be willing to update your OP as discussed above.

@rei2hu Whoa! This is awwwwwwwesssommmme! This has definitely been high on the wish list for some time! Will take a deeper look this evening!

@rei2hu I suppose initial feedback would be whether the file reading can be separated from parsing DSV. My thinking here is whether we might be able to create a parsing...

@rei2hu Considering an incremental parser, I suppose maybe better than a byte-by-byte parser would be an incremental parser which accepts arbitrarily sized chunks (per update).

@rei2hu Couple questions: 1. Have you considered adding support for inferring the separator from provided data? 2. What is the strategy for dealing with headers? 3. Should we make the...

Re: 1. One way to address computational cost is to make such cost tunable. For reference, Python has the builtin [`csv.Sniffer`](https://github.com/python/cpython/blob/3.7/Lib/csv.py#L166) function. For us, may be good enough to, say,...

Re: 2. A "delimiter" event is probably not necessary. I am not sure how that event would be used in userland. Maybe you have use cases in mind? Another approach...