proposal: heredoc comments to allow `+/` in comments, eg from urls or documented unittests
Jonathan M Davis
newsgroup.d at jmdavisprog.com
Sun Feb 11 03:27:19 UTC 2018
On Saturday, February 10, 2018 18:53:03 Walter Bright via Digitalmars-d
wrote:
> On 2/10/2018 6:28 PM, Timothee Cour wrote:
> > all these workarounds are rather ugly; the proposed syntax works all
> > the time (user can just pick a EOC token not in comment) and is analog
> > to existing D heredoc strings, so nothing surprising there.
> > Would PR's be accepted?
>
> You'll need to make a stronger case for it.
>
> D already has 3 kinds of comments. You can pick a different kind if there
> are conflicting characters with one of them. Or use the mentioned escape
> methods.
Personally, the _only_ time that I have ever had a problem with D's nested
comments is when I was working on a lexer. I was forced to use version none
when commenting out code that involved nested comments - especially the unit
tests for malformed comments.
In general, nested comments just work perfectly. So, while dealing with the
rare cases where they're a problem may be annoying, it's just not the sort
of thing that most code has to worry about. And it's already kind of silly
that we have as many comment types as we do.
- Jonathan M Davis
More information about the Digitalmars-d
mailing list