Consider the following code: module test108; // this works and shows up /// Test 1 void test1() { } // doesn't show up mixin("/// Test 2"); void test2() { } // doesn't show up either mixin("/// Test 3 void test3() { }"); If this were fixed, documentation could be moved to an external text file and handled via CTFE and import.
Vote++ I have s pile-o-code that would benefit from this as I am generating functions an would like to be able to generate docs as well. (OT but it would be nice if decent also autocompleted for mixin() code)
This bug is very close to bug 648.
*** Issue 3829 has been marked as a duplicate of this issue. ***
*** Issue 16463 has been marked as a duplicate of this issue. ***
As far as I know, ddoc generation is done right after parsing. This means that by the time the doc is generated the mixin has not been expanded yet.
It's weird... if I look at Ddoc for a string mixin of aliases in a struct, I see the alias symbols (by name), but not any comments the mixin puts on them.