It would be easier to test and more flexible all around if userland code was allowed to pass a Taster class of its own into the Reader or anywhere else that uses it. That way if they wanted to extend the taster class and allow for more possible delimiters, dial in the regex patterns a little more, allow for different character encodings, etc. they could do that by replacing the default taster class used by reader and anything else. Think about what the best way would be to go about this...
I was considering allowing users to set default taster and flavor objects via the CSVelte class. I have physical notes for this somewhere... find them and copy them into this issue.
It would be easier to test and more flexible all around if userland code was allowed to pass a Taster class of its own into the Reader or anywhere else that uses it. That way if they wanted to extend the taster class and allow for more possible delimiters, dial in the regex patterns a little more, allow for different character encodings, etc. they could do that by replacing the default taster class used by reader and anything else. Think about what the best way would be to go about this...