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
I do not know about other scenarios in which Ocaml compiler produces unnecessarily vague location information. I can promise to report them once I spot them.
However, if Merlin has a separate typechecking engine from Ocaml compiler, it may also make sense to fix it in a similar way, because it behaves consistently (imprecisely) with the Ocaml compiler.
Original bug ID: 7315
Reporter: kosik
Assigned to: @gasche
Status: closed (set by @xavierleroy on 2017-09-24T15:33:19Z)
Resolution: fixed
Priority: low
Severity: tweak
Version: 4.03.0
Fixed in version: later
Category: typing
Monitored by: @gasche
Bug description
After typing:
type foo = (unit,unit,unit,unit,unit,unit) bar;;
Ocaml (correctly) reports that:
Error: Unbound type constructor bar
What I do not understand is why the location information is so vague.
Currently Ocaml pin-points the problem to:
"(unit,unit,unit,unit,unit,unit) bar"
Why doesn't it provide a more precise location, i.e. where
"bar"
identifier actually occurs?
Steps to reproduce
echo 'type foo = (unit,unit,unit,unit,unit,unit) bar;;' | ocaml
The text was updated successfully, but these errors were encountered: