JuliaDiff / JuliaDiff/AbstractDifferentiation.jl
Allow arbitrary objects to be backends?
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 138
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Currently the fallbacks in the package constrain the backend type to be an AbstractBackend. Is this necessary? e.g. as I think @oxinabox proposed on Slack, in relation to #11, it would be nice if a user-created ChainRules.RuleConfig could directly be used as a backend. Otherwise, one would probably end up implementing a duplicate object or implementing a loose wrapper around it.
How does this package intend to use these types in a way that can't be satisfied by overloading some interface functions?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the fallback handling and the AbstractBackend type, then review the ChainRules.RuleConfig example and the discussion in issue #11. Determine which interface functions must accept user-created backend objects and what guarantees the package requires; done means the intended backend contract is decided and reflected in the implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100