rei2hu

I've pushed the tests I've been using (I realize I'll have to rewrite their structure too eventually). Six of them are failing and I have some brief comments explaining why...

Alright, I think I got something working for that kind of implementation but instead of taking in raw bytes it takes in characters. This lets it pass the utf8 test...

1. Not really although if it's wanted I have a few ideas on how to do it although it would be very computationally expensive. For a "perfect" solution, the implementation...

I changed the implementation to a class so it could inherit from `EventEmitter`. Right now it will only emit rows i.e. `pd.on('row', (data, rowNumber) => ...)`. I tried to follow...

Current ideas I have for the sniffer/delimiter guesser: 1. It's enabled through option that can be set when passing options to the `DsvParser` and will only take effect if `options.delimiter`...

When picking the delimiter there I imagined that there will be at least 2 conditions that must be fulfilled: 1. A minimum row count 2. All of the internal ratings...

Yes, the delimiter event will only be emitted once and then everything will be normal after that. For the forced guess, the way I imagined the sniffer would work is...

I understand now. With a hard upper limit like you described I see why there's no need for a lot of things I was proposing.

I haven't started on the other files typically found in each package (benchmarks, docs, examples) so I think it's still WIP. For the committed files so far, I plan to...

Thanks for the suggestion! An optional runtime argument to determine the path of the config file could be a possible solution, but I'm not sure if I'll make the update...