Open litlighilit opened 1 week ago
As I tested, at least no error in Nim 2.1.1, 2.0.0, 2.0.4
!nim doc
type O = object
proc `=destroy`*(self: O) = discard
0 (0 bytes)
```cpp
```
2024-06-17T13:23:08
2024-06-17T13:23:08
now
0 (0 bytes)
```cpp
```
2024-06-17T13:23:09
2024-06-17T13:23:09
now
0 (0 bytes)
```cpp
```
2024-06-17T13:23:12
2024-06-17T13:23:12
now
0 (0 bytes)
```cpp
```
2024-06-17T13:23:14
2024-06-17T13:23:14
now
0 (0 bytes)
```cpp
```
2024-06-17T13:23:17
2024-06-17T13:23:17
now
0 (0 bytes)
```cpp
```
2024-06-17T13:23:19
2024-06-17T13:23:19
now
0 (0 bytes)
```cpp
```
2024-06-17T13:23:21
2024-06-17T13:23:21
now
0 (0 bytes)
```cpp
```
2024-06-17T13:23:23
2024-06-17T13:23:23
now
11.4.0
14.0.0
20.3
2024-06-17T13:16:43Z
2
nim doc --run -d:nimDebug -d:nimDebugDlOpen -d:ssl -d:nimDisableCertificateValidation --forceBuild:on --colors:off --verbosity:0 --hints:off --lineTrace:off --nimcache:/home/runner/work/Nim/Nim --out:/home/runner/work/Nim/Nim/temp /home/runner/work/Nim/Nim/temp.nim
:robot: Bug found in 18 minutes
bisecting 8
commits at 0
commits per second
I think theres no "!nim doc" in the bisect bot, I don't know what it should do 🤔 but ideas and pr welcome: https://github.com/juancarlospaco/nimrun-action
Description
A regression, maybe only occur in Nim 2.0.6, not in devel branch or 2.0.4
only causes compile-error when
nim doc
and other commands likenim c
ornim check
just work.Simplest demo:
Nim Version
Nim Compiler Version 2.0.6 [Windows: amd64] Compiled at 2024-06-17 Copyright (c) 2006-2023 by Andreas Rumpf active boot switches: -d:release
Current Output
Expected Output
Possible Solution
No response
Additional Information
I found it shown on nimpylib's test