Open wjones127 opened 2 years ago
I think the cookbook approach is to just show the minimal necessary code within the source file, and not necessarily show how one might separate declarations into headers.
Personally, I think it would be helpful to have two examples:
Thanks! (1) sounds easily doable. For (2), I guess the repo where I have it now (drin/cookbooks.git) is a reasonable place to keep it. I'll try to expand with python bindings. I'll see about how to do R bindings in the near-ish future.
Created a draft PR: https://github.com/apache/arrow-cookbook/pull/227
decided to just mark it ready for review. not sure there's any need to keep it as a draft
I have something that I think would work as an initial pass for this. I have a recipe here:
What would be the best way to move the recipe into this repo to submit a PR? I formatted the directory to be self-contained, but looking at other recipes in this repo, it seems like it's preferred to keep code mostly self-contained within a single source file.
Is there a preference on how to clearly distinguish what is necessary in the header file?
After some suggestions I can prepare an initial PR.