You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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".
The text was updated successfully, but these errors were encountered:
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".
The text was updated successfully, but these errors were encountered: