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

toplevel.pl: fix arity mismatch in read_input/2 #2653

Merged
merged 3 commits into from
Nov 15, 2024

Conversation

srenatus
Copy link
Contributor

@srenatus srenatus commented Nov 1, 2024

I ran into the same problem today and I figured I'd take a stab at it. Unfortunately, I'm not certain it is the right approach, but it no longer errors like it did before.

Fixes #2650.

I ran into the same problem today and I figured I'd take a stab at it.
Unfortunately, I'm not certain it is the right approach, but it no
longer errors like it did before.

Fixes mthom#2650.

Signed-off-by: Stephan Renatus <stephan@styra.com>
@bakaq
Copy link
Contributor

bakaq commented Nov 1, 2024

Damn, I missed this in #2527. I confirm that this is indeed the intended way that this should be fixed, good catch!

@bakaq
Copy link
Contributor

bakaq commented Nov 1, 2024

Actually, this is not enough. If you press p and then Enter it does not end the query as it should. I'm not sure how to fix this.

@srenatus
Copy link
Contributor Author

srenatus commented Nov 1, 2024

If you press p and then Enter it does not end the query as it should.

For my understanding: that is because the branch for C = p only "happens" after we've unified Stop with continue, and once that's done, it cannot ever "go back" to stop?

Signed-off-by: Stephan Renatus <stephan@styra.com>
@srenatus
Copy link
Contributor Author

srenatus commented Nov 2, 2024

Pushed another commit. I think this is closer to the desired behaviour -- it's now "committing" to "continue" much later, only for the explicit "next" input...

Signed-off-by: Stephan Renatus <stephan@styra.com>
Copy link
Contributor

@bakaq bakaq left a comment

Choose a reason for hiding this comment

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

Sorry for the delay. Looks great and I can't see any problems testing this manually!

@mthom mthom merged commit 9f6bbe9 into mthom:master Nov 15, 2024
13 checks passed
@srenatus srenatus deleted the sr/issue-2650 branch November 15, 2024 07:45
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.

Top level: existence error for read_input
3 participants