-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docgen: implement doc link resolution in current module
no special handling of routineKinds here fix segfault fix references in the Manual a supplemental test generics: rm type parameters in normalized names allow underscore in names and export (*) many fixes of warnings: - always resolve all the 3 cases: manual references, RST anchors, Nim anchors and print warnings in case of ambiguity - preserve anchor/substitution definition places - correctly handle `include` in ``.nim`` files for doc comment warnings/errors - make warning messages more detailed change wording & add test regarding brackets in input parameter types some progress: - fixes for handling symbols with backticks - now reference points to concrete function (not group) if there is no other overloads - link text is the full name (with function parameters) if there is only 1 overload. If there are > 1 then it's like "proc binarySearch (2 overloads)" add more testcases, fix func add specification of the feature [skip ci] update the spec reworked the implementation + more tests fix ambiguity handling and reporting, including adding RST explicit hyperlinks to ambiguity printing Default priorities now conform to the `docgen.rst` spec also. enable `doc2tex` fix generics parameters for types some cleanups and clarifications tests on inclusion of .rst & .nim into .nim update forgotten files for tests
- Loading branch information
Showing
22 changed files
with
1,782 additions
and
141 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.