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

please report "module M not found" instead of "unbound value M.foo" #4510

Closed
vicuna opened this Issue Feb 21, 2008 · 1 comment

Comments

Projects
None yet
1 participant
@vicuna
Copy link
Collaborator

vicuna commented Feb 21, 2008

Original bug ID: 4510
Reporter: ecc
Status: closed (set by @damiendoligez on 2012-02-07T14:50:19Z)
Resolution: fixed
Priority: normal
Severity: feature
Version: 3.10.1
Fixed in version: 3.12.0
Category: typing
Monitored by: @glondu @yakobowski

Bug description

When recompiling a program after a period of time, if I get the error message "unbound value SomeLibrary.foo", I can't tell whether SomeLibrary's API has changed (perhaps renaming foo), or simply that SomeLibrary is no longer on the include path. A (simple?) change to the error message would make this much more informative.

In the case where SomeLibrary is found, but there's no foo, I suggest reporting something like "no value foo was found in module SomeLibrary".

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Feb 7, 2012

Comment author: @damiendoligez

Starting with 3.12.0, the compiler reports "unbound value SomeLibrary.foo" in the first case, and "unbound module SomeLibrary" in the second case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.