fix: handle function contexts differently from constant contexts #660
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.
DI source
FunctionContext
andBackendContext
as private subtypes ofContext
, useful in second-order operators when passing stuff to the shuffled first-order operatorConstantOrFunctionOrBackend = Union{Constant,FunctionContext,BackendContext}
DI extensions
DI.Constant
withDI.ConstantOrFunctionOrBackend
in most placesPrepContext
internally for second-order preparation with the rightDual
typeFunctionContext
differently by annotating it asDuplicated
if necessary. Function annotation doesn't work for second-order Enzyme #592 is still not fixed but at least it should error in the second order case.