Skip to content
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

jit and vamp best practices #11

Open
nstarman opened this issue Feb 12, 2024 · 1 comment
Open

jit and vamp best practices #11

nstarman opened this issue Feb 12, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@nstarman
Copy link
Contributor

Just a suggestion to add a small section to the docs about best practices for quaxifying jitted and vmapped functions. Thanks!

@patrick-kidger
Copy link
Owner

At least with JIT, ths usual best-practice of putting JIT at the top level applies.

For vmap, I don't think it matters: put these in whichever order describes the operations you're trying to perform.

Does that sound reasonable to you?

(I agree it'd be worth emphasising this somewhere.)

@patrick-kidger patrick-kidger added the documentation Improvements or additions to documentation label Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants