-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nim doc ..
on a user project is attempting to run runnableExamples from stdlibs, and failing incorrectly [devel] [regression]
#14473
Comments
kaushalmodi
changed the title
May 27, 2020
nim doc ..
is running runnableExamples from stdlibs [devel] [regression]nim doc ..
on a user project is attempting to run runnableExamples from stdlibs, and failing incorrectly [devel] [regression]
@kaushalmodi indeed; this should be fixed in #14439 (I just tried), can you confirm on your end and also for your project that #14439 works? I can revert #14441 also if #14439 will take too long to merge |
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
May 28, 2020
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
May 28, 2020
Araq
pushed a commit
that referenced
this issue
May 28, 2020
…als, and all formatting; other bug fix (#14439) * fix #8871 runnableExamples now preserves source code comments, litterals, and all formatting * remove orig deadcode from getAllRunnableExamplesImpl * fix expected examples * add test to close #14473 * correctly handle regular comments before 1st token inside runnableExamples * add test to answer #14439 (comment) * update tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nim doc ..
is failing because of 2 reasons:sequtils
in this example). This is not expected.toSeq
fromsequtils
in this example).Example
Current Output
Expected Output
Additional Information
nim doc
executions on Travis done using the latest nim devel. Example: https://travis-ci.org/github/kaushalmodi/version/jobs/692027081#L355The text was updated successfully, but these errors were encountered: