error syntax highlighting in func.d#7550
Conversation
|
Thanks for your pull request, @WalterBright! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. |
WalterBright
force-pushed
the
cannot-deduce
branch
3 times, most recently
from
17fdafc to
138f551
Compare
| * License: $(LINK2 http://www.boost.org/LICENSE_1_0.txt, Boost License 1.0) | ||
| * Source: $(LINK2 https://github.com/dlang/dmd/blob/master/src/dmd/func.d, _func.d) | ||
| * Documentation: https://dlang.org/phobos/dmd_func.html | ||
| * Coverage: https://codecov.io/gh/dlang/dmd/src/master/src/dmd/func.d |
There was a problem hiding this comment.
Ddoc's "auto-escaping" rears its head here:
BTW what's the motivation for including Documentation and Coverage on the Ddoc page?
- The user is already on this page
- For Ddox or nightly builds its even a different URL
- Coverage information is not something I expect to be part of the docs?
- If you want something to be done automatic, let us know. It might be more effective.
There was a problem hiding this comment.
That's fixed in later versions of dmd.
There was a problem hiding this comment.
I find those links very convenient when editing source code.
There was a problem hiding this comment.
That's fixed in later versions of dmd.
Oh yes. Actually there's a fix for this setting in the queue for a while already:
I find those links very convenient when editing source code.
I didn't question this, just the fact that you expose them to the user documentation by adding them to the Ddoc header. What was wrong with using // for these two links?
There was a problem hiding this comment.
You used // Online documentation: <url> or // Coverage: <url> as comments before - this had the advantage of not being displayed on dlang.org.
There was a problem hiding this comment.
Ok. I prefer to have them in one Ddoc block.
WalterBright
force-pushed
the
cannot-deduce
branch
5 times, most recently
from
d9a5f6c to
79c8e10
Compare
WalterBright
force-pushed
the
cannot-deduce
branch
from
79c8e10 to
fdf96cb
Compare
4 participants
No description provided.