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

Reduce duplicate tracking of writes in changeset and state

Closed
#4,483 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp

Research direction

Start with the changeset and current-state handling discussed in PR #4352, focusing on how writes are tracked and how deletes differ. Determine whether retaining only deletes is a valid optimization, and document or implement the resulting change with appropriate validation.

Written by the indexing model from the issue text.

Description

    Unless I am missing something, this augments the changeset with all the writes, which mostly duplicate current->state except for deletes. Is that correct? If so, and if this is done for expediency, can we have a ticket that tracks that it's possible to optimise this in the future by adding only deletes here?

Originally posted by @achamayou in https://github.com/microsoft/CCF/pull/4352#discussion_r1014198531

Dominant language
C++
Stars
874
Forks
263
Avg merge
1d 14h
Merged PRs (30d)
157

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 microsoft/CCF

All issues in microsoft/CCF

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.