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: 5293 Reporter: art1 Status: resolved (set by @damiendoligez on 2017-03-03T14:48:55Z) Resolution: suspended Priority: normal Severity: feature Target version: later Category: -for ocamlbuild use https://github.com/ocaml/ocamlbuild/issues Tags: junior_job Monitored by:@jberdine
Bug description
Hello,
the actual behaviour is not very helpful. If the compiler detects circular builds, it will be very hard to find out, what is the reason for this. It would be more helpful if the compiler reports the lines in the involved modules. Very very helpful would be if the compiler also reports a more detailled explanation and give hints for resolving such conflicts.
The text was updated successfully, but these errors were encountered:
Ocamlbuild means:
ocamlbuild foo.native
Circular build detected (foo.cmx already seen in [ foo.cmx;
foo.native ])
Compilation unsuccessful after building 3 targets (0 cached) in
00:00:00.
In my experience, making the mistake of using prefixing something with Foo inside foo.ml is rather common (eg. you're adding a function in list.ml and, out of habit, call List.map instead of map). I think the error message for circular build could be improved at least in that very specialized use-case.
Original bug ID: 5293
Reporter: art1
Status: resolved (set by @damiendoligez on 2017-03-03T14:48:55Z)
Resolution: suspended
Priority: normal
Severity: feature
Target version: later
Category: -for ocamlbuild use https://github.com/ocaml/ocamlbuild/issues
Tags: junior_job
Monitored by: @jberdine
Bug description
Hello,
the actual behaviour is not very helpful. If the compiler detects circular builds, it will be very hard to find out, what is the reason for this. It would be more helpful if the compiler reports the lines in the involved modules. Very very helpful would be if the compiler also reports a more detailled explanation and give hints for resolving such conflicts.
The text was updated successfully, but these errors were encountered: