0

I usually use dune build @check to quickly check if my code can compile. I've run into a number of cases where the command returns a clean output, but doing a dune build . will return a large number of compiler errors.

Is there a reason for this, or am I misusing the check command? I guess I'm mostly thinking about it as an equivalent to cargo check in Rust which will usually find all the compiler errors and is faster than cargo build.

David 天宇 Wong
  • 3,724
  • 4
  • 35
  • 47
  • 2
    What kind of fresh errors do you see when moving from `dune build @check` to `dune build .`? The `@check` target is a minimal target that aims to build metadata for the project. It is normal that some errors are not detected at this stage, but most errors should be covered? – octachron Feb 28 '23 at 13:23

0 Answers0