Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Inline nullary fact is not seeded

Open
#2,231 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
backend

Research direction

Start by tracing how inline facts are parsed and seeded through the easy API, then compare the nullary flag() case with the working unary fact and the insert path described here. Add a regression test for the acceptance example at W=1 and W>1; done when both configurations derive p(100) without an insert.

Written by the indexing model from the issue text.

Description

Found during #2134. Independent of worker count.

An inline nullary fact is not seeded. Through the easy API at W=1, with no insert:

.decl flag()
.decl p(x: int64)
flag().
p(100) :- flag().

A snapshot of p, with or without a step first, returns 0 rows. The unary counterpart works: g(5). p(x) :- g(x). returns p(5). Inserting a flag row with wirelog_easy_insert does derive p(100).

Acceptance

  • flag(). seeds one row of flag, and the program above derives p(100) at W=1 and W>1, covered by a test.
Dominant language
C
Stars
18
Forks
2
Avg merge
8h 15m
Merged PRs (30d)
216

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from semantic-reasoning/wirelog

All issues in semantic-reasoning/wirelog

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.