-
Notifications
You must be signed in to change notification settings - Fork 13
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
Invalid syntax emitted with max_depth/1 #280
Comments
Ok, I (vaguely) see what you are primarily referring to now. Being somewhat
visually impaired these days it often takes me a while to catch on to
subtle visual cues.
…On Sun, Jul 23, 2023 at 3:49 PM UWN ***@***.***> wrote:
?- write_term({A},[max_depth(1)]).
{...) true.
And please reconsider your decision to not show the variable in this case.
—
Reply to this email directly, view it on GitHub
<#280>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFNKSEWRRIPFI53Z427AWSDXRS3NTANCNFSM6AAAAAA2UJK3EI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
infradig
added a commit
that referenced
this issue
Jul 23, 2023
infradig
added a commit
that referenced
this issue
Jul 23, 2023
infradig
added a commit
that referenced
this issue
Jul 23, 2023
UWN_blocking |
What loops?
…On Sun, Jul 23, 2023 at 10:40 PM UWN ***@***.***> wrote:
You give me credit for caring enough to have made a decision on this.
?
In any case, the new version just loops.
—
Reply to this email directly, view it on GitHub
<#280 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFNKSEXXKPMMFWK6ASC54QTXRULUNANCNFSM6AAAAAA2UJK3EI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
And please reconsider your decision to not show the variable in this case.
The text was updated successfully, but these errors were encountered: