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: 1363 Reporter: administrator Status: closed Resolution: won't fix Priority: normal Severity: feature Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Emmanuel Renieris
Version: Any
OS: Any
Submission from: miette.cs.brown.edu (128.148.38.66)
-i is a very useful option. Unfortunately, when type inference fails, -i gives
no output. Is it possible to see the types that were inferred? It would help
find the
error sometimes. I know you are working on a long-term solution to this, but
maybe
this is not too hard to include quickly.
Thanks,
Manos
The text was updated successfully, but these errors were encountered:
-i is a very useful option. Unfortunately, when type inference
fails, -i gives no output. Is it possible to see the types that were inferred? It would help find the error sometimes. I know you
are working on a long-term solution to this, but maybe this is not
too hard to include quickly.
This would not be very difficult indeed, but you have already two ways
to do it using other tools:
using #use with ocaml (you need to load all other modules
first... but it is enough to put them on the command line when
calling ocaml)
using the typeckeck feature of the editor in ocamlbrowser
additionally, you can inspect internal types for properly typed
phrases.
Original bug ID: 1363
Reporter: administrator
Status: closed
Resolution: won't fix
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Emmanuel Renieris
Version: Any
OS: Any
Submission from: miette.cs.brown.edu (128.148.38.66)
-i is a very useful option. Unfortunately, when type inference fails, -i gives
no output. Is it possible to see the types that were inferred? It would help
find the
error sometimes. I know you are working on a long-term solution to this, but
maybe
this is not too hard to include quickly.
Thanks,
Manos
The text was updated successfully, but these errors were encountered: