Bug 22661 – Functions cannot be interpreted while being compiled

//////////////////// parent.d ///////////////////// import childb; import defs; class Parent { enum CONSTANT = defs.CONSTANT; } //////////////////// childa.d ///////////////////// import parent; import helpers; class ChildA : Parent { mixin(ctfeFunc(true)); } //////////////////// childb.d ///////////////////// import parent; import helpers; class ChildB : Parent { mixin(ctfeFunc()); } ///////////////////// defs.d ////////////////////// import childa; enum CONSTANT = ""; //////////////////// helpers.d //////////////////// string ctfeFunc(bool) { import std.ascii; return ""; } string ctfeFunc() { return ctfeFunc(false); } /////////////////////////////////////////////////// Compiling the above code with dmd -c parent.d results in the following error: helpers.d(1): Error: function `helpers.ctfeFunc` circular dependency. Functions cannot be interpreted while being compiled childa.d(5): called from here: `ctfeFunc(true)` helpers.d(8): called from here: `ctfeFunc(false)` childb.d(5): called from here: `ctfeFunc()`

Whoa, can this compile even in theory? Four modules import each other and you have a circular dependency between declaration stage and semantic stage.

This example compiles just fine with current dmd, see https://run.dlang.io/is/9koFtR.

I can see the error on run.dlang.io, too, after adding the filename as an argument: https://run.dlang.io/is/QmWZ9j The error seems to depend on the order of files on the dmd command line.

THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dmd/issues/20037 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB