Bug 20431 – Allow a Mixin Type to resolve to an expression where it makes sense

When Mixin Types were introduced in the grammar they took over Mixin Expressions in a few places in the parser such as in template parameters or array declarations. This code stopped working fun!(mixin("(a) => ++a"))(); // void fun(alias t)(){} int[mixin("4")] b; auto c = new int[mixin("4")]; and the following started to work fun!(mixin("MyType"))(); int[mixin("string")] d; However, with the fix to issue 20388, mixins in template arguments were restored back to be parsed as expressions to not break code. A more consistent solution would be to allow both a type or an expression in Mixin Types specially for the template argument case.

@BorisCarvajal updated dlang/dmd pull request #10629 "Better fix for issue 20388" fixing this issue: - Fix issue 20431 - Allow a Mixin Type to resolve to an expression https://github.com/dlang/dmd/pull/10629

dlang/dmd pull request #10629 "Fix issue 20431 - Allow a Mixin Type to resolve to an expression" was merged into stable: - ece7f2cd978ab5e2138f0ccdcf176aaebebde569 by Boris Carvajal: Fix issue 20431 - Allow a Mixin Type to resolve to an expression https://github.com/dlang/dmd/pull/10629