Spurious "Cyclic macro dependencies" error with pipelining turned on about scala3 HOT 2 CLOSED

from debugging so far it seems like a problem in macro splicing, suddenly there are far more "missing class" suspensions that do not appear without pipelining.

from scala3.

This is looking closer to a problem of build configuration - i.e. if a macro in project b uses a class in project a, then pipelining will need to be disabled on project a, but the error message is obscure.

E.g. in DFiant it looks like there is a class from the compiler_ir module being used in a macro in core, causing missing class error when invoking the macro. I'm working on improving reporting here.

Edit: it is still classed as a bug, because the error being reported is incorrect, it should be another error instead

from scala3.