Treat pairs(NamedTuple) as NamedTuple for indexing
#1286
Merged
Conversation
This file contains 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
This prevents issues with double-counting when using kwargs.
ToucheSir
force-pushed
the
bc/pairs-kwarg-indexing
branch
from
bb59a41
to
24a6111
Compare
mcabbott
approved these changes
Aug 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This prevents issues with double-counting when using kwargs.
A note on test changes: A couple which were returning natural tangents for unused numeric fields are now returning
nothing. I've opted not to try projecting those nothings to the original number type after seeing the feedback on JuliaDiff/ChainRulesCore.jl#574, but perhaps not doing so causes deleterious effects downstream?Fixes #1284.