Comment #0 by default_357-line — 2008-10-15T13:10:40Z
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.
Comment #1 by shro8822 — 2008-10-15T16:46:16Z
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)
Comment #2 by leandro.lucarella — 2008-12-08T08:45:55Z
This bug is very close to bug 648.
Comment #3 by braddr — 2010-02-18T21:28:20Z
*** Issue 3829 has been marked as a duplicate of this issue. ***
Comment #4 by andrej.mitrovich — 2016-09-04T17:22:47Z
*** Issue 16463 has been marked as a duplicate of this issue. ***
Comment #5 by razvan.nitu1305 — 2019-09-09T15:07:25Z
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.
Comment #6 by default_357-line — 2019-09-10T13:34:15Z
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.
Comment #7 by robert.schadek — 2024-12-13T17:48:55Z