JuliaDiff / JuliaDiff/ChainRulesCore.jl
`Reusable` and `NonReusable` reverse mode capability
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 267
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
From discussion on Slack with @chengchingwen
The idea is to define a new capabilities Reusable which means that the pullback can be called multiple times, and NonReusable, which means that the pullback can only be called once.
NonReusable can be useful when wanting to save allocations, such as in https://github.com/JuliaDiff/ChainRulesTestUtils.jl/issues/264
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
No files, tests, or entry points are named. Start by locating the reverse-mode capability definitions and pullback handling in ChainRulesCore.jl, then read the linked ChainRulesTestUtils issue for context. Done means the Reusable and NonReusable capabilities are defined with clear semantics for repeated versus single pullback calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100