merely inspecting *1 *2 *3 should not affect history
Open
Nobody has claimed this yet.
bug
- Dominant language
- Clojure
- Stars
- 301
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
(tests
:foo
*1 := :foo) ; pass
(tests
:foo := :foo
*1 := :foo) ; fail, imo should pass
(tests
(inc 1)
:= 2
(dec *1) ; example usage (currently fails)
:= 1)
(tests ; real-world usage
(analyze {} '(+ 2 3))
:= [[[:apply [:global :clojure.core/+] [:literal 2] [:literal 3]]]
[[:literal nil]]]
(emit (comp symbol str) (first *1)) ; first says – ignore remote part, consider local part only
:= `(r/peer 0 0 0 0
(fn [~'context]
(do (m/latest u/call (r/steady +) (r/steady '2) (r/steady '3)))))
)
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 or tests are named in the issue. Start by reproducing the three Clojure examples in the RCF test macro, then trace how history is updated when expressions are inspected; done means inspecting *1, *2, or *3 does not change the value seen by later expressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100