patrick-kidger / patrick-kidger/diffrax
callable paths
Open
Nobody has claimed this yet.
question
refactor
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 189
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 1
Description
Paths now use path.evaluate(). It would be more useful to use a call method instead. This is more in line with the other classes and allows us to use other callable control inputs that need not be derived from AbstractPath.
Contributor guide
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 file or test is named. Start by locating AbstractPath, path.evaluate(), and current path call sites, then compare neighboring callable classes. Done means path controls use the callable interface and other callable inputs can work without deriving from AbstractPath, with the relevant existing tests updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100