Skip to content

aggressive reparenting of trailing delimiter after cut #166

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

Open
disconcision opened this issue Mar 21, 2025 · 1 comment
Open

aggressive reparenting of trailing delimiter after cut #166

disconcision opened this issue Mar 21, 2025 · 1 comment

Comments

@disconcision
Copy link
Member

Not sure if this is a bug, but definitely an interesting source of possible confusion. Given:

Image

Cutting produces:

Image

this occurred during ER's task 4; they had already felt they had stubbed out a separate dist definition at the top with an empty definition, and were going to move content to the definition. but after the cut, the orphan in in the body of the fun gets reparented to the new let, which then makes the fun part of the new let's definition

@disconcision disconcision changed the title aggressive reparenting of in after cut aggressive reparenting of trailing delimiter after cut Mar 21, 2025
@disconcision
Copy link
Member Author

disconcision commented Mar 21, 2025

Here's another example from EE2, that was sort of serendipitous but also surprising:

given:

Image

cutting yields:

Image

so you end up in the hole that you wanted to fill and can just paste

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant