[Docs] [AutoDiff] Allow implicitly inherited '@differentiable' on non-public protocol req impls. #29307
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.
Currently, when a conforming type implements a
@differentiable
protocol requirement, the corresponding conforming implementation is required to have at least a@differentiable
that covers all differentiability parameters in the protocol requirement. However, this is not a great design for usability because developers almost always start with missing@differentiable
and getting a compilation error. This also makes ML models built with libraries that use differentiable programming more verbose than those built with other ML frameworks.We agreed during this Friday's design review to allow
@differentiable
to be implicitly inherited from protocols when the conforming implementation is non-public.