dnolen: In my macro I call a function say my.ns/myfn and then I use that macro in my.ns2 on which my.ns depends without noticing it. First the compiler will complain that my.ns does not exist in my.ns2. I then require it at the top. Then I've created a circular dependency but I never call a function in my.ns explicitly in my.ns2 but only through the macro. This circular dependency was not picked up by the compiler when compiling in parallel. Instead the compilation just deadlocks and I have to kill the process. Not sure if it's clearer now? Would like to create a minimal reproduceable version of it but I'm quite swamped with work so atm I don't have time unfortunately.

right but this isn’t supported anyway

remove the circular dependency

The issue is not that the circular dependency is not supported, it’s that the compiler won’t tell me that I have a circular dependency as it normally does but it will just freeze up instead. The expected behaviour would be to throw an error saying that I have a circular dependency (like it does without parallel compilation) but instead it just freezes without giving me a hint what the issue is.

the circular dependency check we have for explicit cases

you have an implicit case

an issue for that is welcome, but we’ll need a minimal repro in the ticket which will probably be somewhat challenging to construct

Exactly, ok when I get time for it I’ll try to flesh out a minimal repro and file a ticket