JuliaDiff / JuliaDiff/ChainRulesCore.jl
What to do if `@thunk` is applied to a variable (rather than an expression) ?
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 267
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
maybe make @thunk error if applies to a variable (rather than an expression) ? #50
I can imagine an easy mistake to make would be to write:
∂A = foo(x)
return @thunk(∂A)
When one whould have written:
∂A = @thunk(foo(x))
return ∂A
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
The issue names only the @thunk entry point; start there and trace how it receives a variable versus an expression. Resolve whether the variable form should error, and document or test the selected behavior for both examples.
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
- 20/100