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.

Sign up for GitHub

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

Jump to bottom

A 1->2+2->1 rule with indices eats up the next edge #283

Open
joanise opened this issue Sep 1, 2023 · 1 comment
Open

A 1->2+2->1 rule with indices eats up the next edge #283

joanise opened this issue Sep 1, 2023 · 1 comment

Comments

@joanise
Copy link
Collaborator

joanise commented Sep 1, 2023

Given mapping [{"in": "d{1}ef{2}", "out": "gh{1}i{2}"}] whenever def occurs in the input, the output is correct, but the next edge disappears. E.g., with input deft the output is correct. ghit, but the edges are [(0, 0), (0, 1), (1, 2), (2, 2)] instead of [(0, 0), (0, 1), (1, 2), (2, 2), (3, 3)]
joanise added a commit that referenced this issue Sep 1, 2023
@joanise
test: MRE for #283 shows swallowed edge after 1->2+2->1
91d46f6
@joanise joanise mentioned this issue Sep 1, 2023
Merged
joanise added a commit that referenced this issue Nov 15, 2023
@joanise
test: MRE for #283 shows swallowed edge after 1->2+2->1
d0373e9
@joanise
Copy link
Collaborator Author

joanise commented Nov 15, 2023 •
edited
Loading

Rebased dev.issue-283 onto main, the bug still persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joanise