wesm opened a new issue, #20: URL: https://github.com/apache/arrow-nanoarrow/issues/20
In the spirit of making vendoring simpler for users, I'm wondering what we can do to reduce the total number of files in the project. In very large projects that are intending to be vendored (like DuckDB or SQLite), they implement an amalgamation that does a topological sort of dependencies and stitches together all the files to create one big header and one big compiled file. I see two different approaches here: * Do all the implementation work in a single .C file and try to make it as brief as possible * Implement an amalgamation similar to DuckDB or SQLite. If you look at https://github.com/nanopb/nanopb, there are 4 headers and 3 .C files. Do you think we could get closer to that? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
