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: 4716 Reporter: Yoric Assigned to:@garrigue Status: closed (set by @garrigue on 2010-04-30T07:12:46Z) Resolution: fixed Priority: normal Severity: feature Fixed in version: 3.12.0+dev Category: ~DO NOT USE (was: OCaml general) Monitored by:@glondu
Bug description
Beginners are often baffled by error message "This expression has type foo but is used with type foo", due to having two types with the same name in the toplevel.
I suggest that, whenever the toplevel is instructed to print an error messages that that two types are incompatible, it first checks whether the pretty-printed types are identical, in which case it rather prints a message along the lines of
"This expression has type foo but is used with type foo. This strange error message is due to the fact that you have define two types with the same name and are attempting to use a value corresponding to one definition as if it belonged to the other definition."
The text was updated successfully, but these errors were encountered:
Original bug ID: 4716
Reporter: Yoric
Assigned to: @garrigue
Status: closed (set by @garrigue on 2010-04-30T07:12:46Z)
Resolution: fixed
Priority: normal
Severity: feature
Fixed in version: 3.12.0+dev
Category: ~DO NOT USE (was: OCaml general)
Monitored by: @glondu
Bug description
Beginners are often baffled by error message "This expression has type foo but is used with type foo", due to having two types with the same name in the toplevel.
I suggest that, whenever the toplevel is instructed to print an error messages that that two types are incompatible, it first checks whether the pretty-printed types are identical, in which case it rather prints a message along the lines of
"This expression has type foo but is used with type foo. This strange error message is due to the fact that you have define two types with the same name and are attempting to use a value corresponding to one definition as if it belonged to the other definition."
The text was updated successfully, but these errors were encountered: