TimelyDataflow / TimelyDataflow/differential-dataflow
`distinguish_since` is a terror
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 211
- Avg merge
- 10h 42m
- Merged PRs (30d)
- 34
Description
At the moment users must manually call distinguish_since to unblock physical merging of batches. This seems like a mis-feature, and should probably be handled automatically, perhaps with capability-like "bookmarks" that allow a user to subset batches up to that point. This would simplify several APIs and reduce a fairly consistent source of confusion.
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
The issue names the distinguish_since API but no files, tests, or entry points. Start by reading the existing distinguish_since implementation and its callers, then determine the intended automatic batching and bookmark semantics; done would require an agreed design and corresponding API simplification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100