Enable vmap over equinox modules #16
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(Bump hash to trigger test workflow)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #15
This does introduce a dependency to cachetools to use an LRU cache with custom keys.
Further, a dummy pass is still required through any module being vmapped over. In idiomatic equinox code, where modules will quite often vmap over nested modules, this is perhaps not ideal, as it can require manually performing dummy passes over deeply nested modules. Perhaps some further work could be done to allow vmap to automatically trigger a dummy pass on its first call? This could be of use in use cases beyond equinox as well.