Progressive list

[michaelsproul]

No description provided.

[michaelsproul]

Hi @copilot, could you try implementing an iterator over ProgTree which wraps an iter::Iter instance and keeps track of the next ProgNodes to continue iterating from? The iterator should iterate all elements in the first right child, and then the right child of the first left child, right child of the second left child, and so on. The ProgTree structure is represented by this diagram below:

        root
         /\
        /  \
       /\   1: chunks[0 ..< 1]
      /  \
     /\   4: chunks[1 ..< 5]
    /  \
   /\  16: chunks[5 ..< 21]
  /  \
 0   64: chunks[21 ..< 85]

For more details you can also read EIP-7916: https://eips.ethereum.org/EIPS/eip-7916.

[Copilot]

@michaelsproul I've opened a new pull request, #84, to work on those changes. Once the pull request is ready, I'll request review from you.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 79.50664% with 108 lines in your changes missing coverage. Please review.
✅ Project coverage is 75.54%. Comparing base (8963bc5) to head (883e818).

Files with missing lines	Patch %	Lines
src/progressive_tree.rs	78.40%	46 Missing ⚠️
src/progressive_list.rs	81.15%	36 Missing ⚠️
src/any_list.rs	80.83%	23 Missing ⚠️
src/context_deserialize.rs	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #82      +/-   ##
==========================================
+ Coverage   70.15%   75.54%   +5.38%     
==========================================
  Files          22       25       +3     
  Lines        1280     1803     +523     
==========================================
+ Hits          898     1362     +464     
- Misses        382      441      +59     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[michaelsproul]

Hey @copilot, can you try adding ProgressiveList to the proptest suite of tests in src/tests/proptest/operations.rs? You'll need a new ProgressiveSpec data structure that doesn't have a length limit (no N), but you can reuse the same Op structure as we should support all of the same ops eventually (for now their implementations on ProgressiveList can be no-ops if not implemented). You'll want to write a new function apply_ops_progressive_list.

[Copilot]

@michaelsproul I've opened a new pull request, #89, to work on those changes. Once the pull request is ready, I'll request review from you.

[macladson]

We can probably assemble as we go instead, but I'm not sure how much value that adds