Switching to using an instance of the SmarterCSV::Reader class

[tilo]

this PR fixes issues around SmarterCSV being thread-safe, e.g. in response to #277

This PR moves away from using a module method, e.g. SmarterCSV.process,
and instead using an instance reader = SmarterCSV::Reader that contains state, and calling reader.process on it.

For backwards compatibility there is a shim that allows existing code to use SmarterCSV.process for the simplest cases, but it no longer gives access to the internal state, e.g. headers, raw_headers, ...

Please update your code to the new calling mechanism.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (a906f19) to head (f6270e1).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #279   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           11        12    +1     
  Lines          380       435   +55     
=========================================
+ Hits           380       435   +55     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jpcamara]

The overall approach looks great. Definitely like just making a distinct new Reader class and wrapping that. I've only been able to skim things so far, but seems like it would fix the threading issues!

[tilo]

The overall approach looks great. Definitely like just making a distinct new Reader class and wrapping that. I've only been able to skim things so far, but seems like it would fix the threading issues!

I ran your test for a long time, and no thread safety issues.

[tilo]

@jpcamara @contentfree I'm releasing this as 1.12.0.pre1

[chaadow]

hi @tilo thanks for merging this! Is it possible to update the Changelog to make it clear that this gem has become thread safe thanks!

[tilo]

hi @tilo thanks for merging this! Is it possible to update the Changelog to make it clear that this gem has become thread safe thanks!

thanks for pointing that out! done!