Open azylman opened 9 years ago
(some of these can be done in a backwards compatible manner if we don't mind adding cruft)
Just for my learning's sake, if all the sinks are in the package, does that mean changing 1 sink would require recompile of the whole package? Not a concern for this repo, just wanted to know.
This package is never compiled on its own, since it's a library. It's only compiled when some program imports it and is built.
Would the first two have a significant effect on binary size, since now you have to compile all sources and sinks into your program?
It will have an effect, but they're all small enough that I expect it to be small On May 27, 2015 5:07 PM, "Rafael" notifications@github.com wrote:
Would the first two have a significant effect on binary size, since now you have to compile all sources and sinks into your program?
— Reply to this email directly or view it on GitHub https://github.com/Clever/optimus/issues/16#issuecomment-106116508.
Wishlist:
Replace Fieldmap
with SafeFieldmap
(https://github.com/Clever/optimus/pull/52)
sources
package instead of having their own packagessinks
package instead of having their own packagescsv
source and sink that take inio.Reader/Writer
s in favor ofcsv.Reader/Writer
sjson
source and sink configurable to be either an array of JSON documents or newline-separate JSON documents (this should probably be done prior to v4 in a backwards-compatible way, so we know what works before we remove the old method)sources/error/ErrorTable
to pass linting (error.ErrorTable stutters, should be error.Table or something - alternatively move this package to internal since it's primarily used for tests)