[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 Nick Sabalausky changed: What|Removed |Added Resolution|WONTFIX |FIXED ---

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 Walter Bright changed: What|Removed |Added Severity|normal |enhancement --

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 Martin Nowak changed: What|Removed |Added CC||c...@dawg.eu --- Comment #8

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 --- Comment #6 from Nick Sabalausky cbkbbej...@mailinator.com --- This is happening in function Lexer::combineComments in lexer.c. The function combines consecutive doc comments, like: /++ comment 1 +/ /++ comment 2 +/ /** comment 3 */ /**

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 --- Comment #7 from Nick Sabalausky cbkbbej...@mailinator.com --- Pull Request: https://github.com/D-Programming-Language/dmd/pull/4745 --

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 Nick Sabalausky cbkbbej...@mailinator.com changed: What|Removed |Added CC|

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 --- Comment #2 from Sönke Ludwig slud...@outerproduct.org --- Do you know if that been a concious decision or is it just an artefact of the implementation? I don't think it makes much sense as it is. Personally I always use /** */ style comments, but

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 --- Comment #1 from Kenji Hara k.hara...@gmail.com --- (In reply to Sönke Ludwig from comment #0) --- /// This function is here to aid in making your /// software do cool stuff. void foo() {} --- It's equivalent with: --- /** This function is

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 --- Comment #3 from Kenji Hara k.hara...@gmail.com --- (In reply to Sönke Ludwig from comment #2) Do you know if that been a concious decision or is it just an artefact of the implementation? I don't think it makes much sense as it is. Personally I

[Issue 14413] Spurious newline in ddoc JSON output for multiple successive line doc comments

https://issues.dlang.org/show_bug.cgi?id=14413 --- Comment #4 from Sönke Ludwig slud...@outerproduct.org --- Just that concatenation as paragraphs instead of concatenation as lines precludes the use of this documentation style: /// This is the summary, possibly going /// over multiple lines. ///