Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement internal node-cursor forwarding #309

Merged
merged 17 commits into from
Jan 30, 2023

Conversation

alexreinking
Copy link
Contributor

@alexreinking alexreinking commented Jan 30, 2023

Implements node-only forwarding for internal cursors over the following edit operations:

  • Insert
  • Delete
  • Replace
  • Move
  • Wrap

The implementation of move is complicated. Unexpectedly so. I've tried to write useful tests for all of these, but we might still encounter bugs. We need to stay diligent about adding test cases for bugs we fix.

Closes #278

@codecov-commenter
Copy link

codecov-commenter commented Jan 30, 2023

Codecov Report

Merging #309 (1f43d9c) into master (42161ae) will decrease coverage by 0.05%.
The diff coverage is 92.96%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@            Coverage Diff             @@
##           master     #309      +/-   ##
==========================================
- Coverage   86.30%   86.25%   -0.05%     
==========================================
  Files          73       73              
  Lines       16487    16537      +50     
==========================================
+ Hits        14229    14264      +35     
- Misses       2258     2273      +15     
Impacted Files Coverage Δ
tests/test_internal_cursors.py 97.44% <90.47%> (-2.56%) ⬇️
src/exo/internal_cursors.py 94.94% <95.74%> (-0.69%) ⬇️
src/exo/pattern_match.py 90.90% <0.00%> (-0.70%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Copy link
Member

@yamaguchi1024 yamaguchi1024 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM if it's ready to merge. Can #278 be closed because of this?

@alexreinking
Copy link
Contributor Author

LGTM if it's ready to merge. Can #278 be closed because of this?

Yes. This is a better implementation.

@alexreinking alexreinking merged commit 86f2a15 into master Jan 30, 2023
@alexreinking alexreinking deleted the cursor/forward-only-nodes branch January 30, 2023 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants