-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[C++] Add example of writing a user-defined compute kernel #174
Comments
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. |
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: #227 |
decided to just mark it ready for review. not sure there's any need to keep it as a draft |
Trying to see if moving these recipe labels captures C++ code blocks outside of function bodies
I am trying the literalinclude directive first before trying to use recipe directives in comments
No description provided.
The text was updated successfully, but these errors were encountered: