Put some guards on types allowed in TaylorTangents #220
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.
Not a high priority, and I am not sure if we want to do this.
Hopefully it is zero overhead by I am yet to check.
I found a case in the wild where I had screwed this up, by putting a
ZeroTangent
somewhere that should have gotten aZeroTangent()
.It's possible to screw this up both in Diffractor itself, but also in rule definitions. (though CRTU.jl will protect against the later)
It is nice to error as close to the creation of the bad type as possible to help work out what is triggering it