Timothee Cour

@a-mr > Probably we can also study how it's done in sphinx we can do better than requiring users to write `:py:const:` or `:py:class:`, because nim is strongly typed and...

after https://github.com/nim-lang/Nim/pull/17372, there's now another, possibly better option: ``` strutils.delete_ instead of: `strutils.delete`_ ``` example: ```nim ##[ foo1_ foo.bar2_ works with a comma separating links too: foo.bar3_, foo.bar4_ `foo.bar5`_ `foo.bar6`_,...

@a-mr if you want to tackle this I'm happy to help, I think your previous contributions to docgen/rst (2 pass approach, underscore link support, sorting, etc) should make this more...

> Let us assume that we are talking about `` `strutils.delete`_`` * shouldn't that be: `` strutils.delete_`` ? (as enabled by your merged PR https://github.com/nim-lang/Nim/pull/17372) eg: ```nim # good: ##...

> Please ensure backwards compatibility, links are shared and kept around for good. multiple anchors can be generated for a section/div/etc so that's fine > pkg/regex.findAllBounds_ this would be an...

interesting.. that means that simply generating extra anchor with the desired form (pointing to 1st overload) should "just work" at least for symbols within same module for symbols within other...

> for whole group of procs: split_ — most often case and hence short. yes, this is what should almost always be used; whether a proc is split into multiple...

> we will emit a warning that there is an ambiguity at what time do you issue a warning? it's about whether the context is known to nim doc or...

oh actually there's a really simple solution to this problem: we can rely on index files (or reuse/augment the one that's generated via `nim doc` which IIRC implies `--index`; preferably...

for separate nim doc invocations, see how it's done in kochdocs; this works (but needs better documentation, PR welcome): ``` nim doc --outdir:/tmp/d19 --index lib/pure/strutils nim doc --outdir:/tmp/d19 --index lib/pure/os...