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 PR does several things that make basically no user facing change.
It was the follow up to #224 but actually ended up way more involved.
ExplictTangentBundle[CanonicalTangentIndex(i)]
(which is funny that it was missing as that's the natural way to index anExplictTangentBundle
getindex
main definitions down on to to the tangent types.Uniform->Taylor/Explict
andTaylor->Explict
, though in future we could put the other way around in (but they are not always going to be defined)hash
for everything, this just uses thehash
of the primal for bundles, which I think is actually sufficient. I am making the assumption that we do not end up needing a dict which stores the same primal with different tangents a ton of times. We can revisit that later if it comes up.ProductTangent
, as we were not using it, and I didn't want to implement the above for it. (I thinkProductTangent
was basically the same asCompositeTangent
but less complete, and that's gone now anyway)