Rules error
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with the linked gist and the (connected x y) function, then reproduce the Cartesian-grid case where (= x y) omits neighbors that also satisfy that condition. Compare it with the non-equal case and determine whether the behavior comes from the reported code or Datascript. Done means identifying the cause and confirming the expected diagonal-neighbor set.
Written by the indexing model from the issue text.
Description
After asking a couple of questions on the datascript slack, @tonsky asked me to make a gist with my error in it. The function (connected x y) should return a set of all diagonal neighbors of neighbors on a cartesian grid but in cases where the (= x y) it ignores neighbors that are also (= x y).
The gist is at https://gist.github.com/Tavistock/6305de1b890e3a60489544ae139b102f. for background this is for implementing a game of checkers or draughts.
This image shows the degenerate case where the orange highlighted checker is selected and the green squares are it's connected. Notice that (= x y) for the checker.
This image shows the correct highlighting when selecting a different piece and using connected. Notice that (!= x y) for the checker.
My question is whether there is an error in my code and reasoning, or if this is a problem with Datascript.
- Dominant language
- Clojure
- Stars
- 5.8k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
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.
More from tonsky/datascript
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
tonsky/datascript#498 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
tonsky/datascript#489 ·
-
Stack overflow when transacting :db.type/tupleAttrs with a :db.type/ref attr through :db.fn/call Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tonsky/datascript#483 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tonsky/datascript#470 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tonsky/datascript#441 · 1 comment · 3 reactions ·
All issues in tonsky/datascript
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
.Needs Triage .Team/UXWest Priority:P3 Type:New Feature
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
clojure-lsp/clojure-lsp#2469 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100