Generating ddoc from the following code results in an error: code: /// void dummy() { } /// Testing _name unittest { assert( true ); } error: $ dmd -main -D ddoc.d ddoc.d(2): Error: function ddoc.dummy unmatched --- in DDoc comment The error goes away if you remove the underscore, or wrap it in quotes ("_name") and it seems to only occur in documentation comments before unittests.
Same error in my case, although, with different DDoc string. It happens after upgrading my project from 2.066 to 2.067: /// Lexical type of a string literal enum StringFormat : ubyte { /// string quoted with '"' Quoted = 0, /// wysiwyg quoted string starting with 'r"' RWysiwyg, /// wysiwyg string quoted with '`' (245:) BackquoteWysiwyg, /// hexadecimal quoted string starting with 'x"' Hex } gives: src/les/lexer.d(245): Error: enum member les.lexer.StringFormat.BackquoteWysiwyg unmatched --- in DDoc comment
(In reply to Ludovit Lucenic from comment #1) > Same error in my case, although, with different DDoc string. It happens > after upgrading my project from 2.066 to 2.067: > > /// Lexical type of a string literal > enum StringFormat : ubyte { > /// string quoted with '"' > Quoted = 0, > /// wysiwyg quoted string starting with 'r"' > RWysiwyg, > /// wysiwyg string quoted with '`' > (245:) BackquoteWysiwyg, > /// hexadecimal quoted string starting with 'x"' > Hex > } > > gives: > > src/les/lexer.d(245): Error: enum member > les.lexer.StringFormat.BackquoteWysiwyg unmatched --- in DDoc comment I forgot to mention that changing the line 244 to: /// wysiwyg string quoted with '`'` removes the compiler error.
THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dmd/issues/18930 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB