-
Notifications
You must be signed in to change notification settings - Fork 130
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
Unexpectedly no type error for invalid module qualification #2685
Comments
Should
|
SICStus and SWI agree here. |
mthom
added a commit
that referenced
this issue
Dec 20, 2024
Now: ?- X:true. error(type_error(atom,user:_514:true),call/0), unexpected. I have not specified the type of |
|
mthom
added a commit
that referenced
this issue
Dec 25, 2024
Thank you a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned in #2684 (comment):
In fact, we also have:
The text was updated successfully, but these errors were encountered: