TimelyDataflow / TimelyDataflow/differential-dataflow
Question about some codes in `arrangement.rs`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 211
- Avg merge
- 10h 42m
- Merged PRs (30d)
- 34
Description
In commit 9d33cda130421c7c391c2fb9d89c55e8d5752c1f, file src/operators/arrange/arrangement.rs, lines 647, it seems that new_capabilities only holds the lower bound of batcher.frontier().
Is it impossible for capabilities to hold a capability which is greater than any one of batcher.frontier(), and need to be held by new_capabilities? Maybe I'm not so familiar with capability.
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
Start by reading commit 9d33cda130421c7c391c2fb9d89c55e8d5752c1f and src/operators/arrange/arrangement.rs around line 647, then trace how capabilities and batcher.frontier() are related. Resolve whether new_capabilities must retain capabilities beyond the frontier; done means documenting the invariant or identifying a concrete correctness issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100