We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
type ## Foo type Foo* = object s: seq[int] proc `=destroy`(foo: Foo) = `=destroy`(foo.s)
Compiling nim c|cpp foo.nim works. Trying to generate documentation using nim doc foo.nim fails.
nim c|cpp foo.nim
nim doc foo.nim
Nim Compiler Version 2.0.0 [Linux: amd64] Compiled at 2023-08-01 Copyright (c) 2006-2023 by Andreas Rumpf
git hash: a488067 active boot switches: -d:release
[...]/foo.nim(7, 13) Error: type mismatch Expression: `=destroy`(foo.s) [1] foo.s: seq[int] Expected one of (first mismatch at [position]): [1] proc `=destroy`(foo: Foo) [1] proc `=destroy`[T](x: var T)
If the code compiles, then the documentation generation should too. Either both should fail or both should work.
The text was updated successfully, but these errors were encountered:
Probably, it is a bug of documentation generation: nim doc --mm:orc test6.nim seems to work for me
nim doc --mm:orc test6.nim
Sorry, something went wrong.
I thought --mm:orc was the default configuration if you specified nothing.
Anyway, thanks for the workaround
fixes #23065; DocLike command defaults to ORC
2014189
fixes #23065; DocLike command defaults to ORC (#23075)
7e4060c
fixes #23065
fixes nim-lang#23065; DocLike command defaults to ORC (nim-lang#23075)
c8649a1
fixes nim-lang#23065
ringabout
Successfully merging a pull request may close this issue.
Description
Compiling
nim c|cpp foo.nim
works. Trying to generate documentation usingnim doc foo.nim
fails.Nim Version
Nim Compiler Version 2.0.0 [Linux: amd64]
Compiled at 2023-08-01
Copyright (c) 2006-2023 by Andreas Rumpf
git hash: a488067
active boot switches: -d:release
Current Output
Expected Output
If the code compiles, then the documentation generation should too. Either both should fail or both should work.
The text was updated successfully, but these errors were encountered: