You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# no warning if removed
{.experimental: "codeReordering".}
# no warning if `` quotes are removed or args are renamedproc`bug`*(x: int, q: float, r: string): string=$(x + q.int) & r
# warning if it's named x, q, or r# no warning if this isn't a proc/funcprocx*=discard
I am receiving a warning under the conditions mentioned in the comments:
/home/kyle/dev/dbTransfer/minimal.nim(5, 1) Warning: Circular dependency detected. codeReordering pragma may not be able to reorder some nodes properly:
line 5 depends on line 10: one declares "x" and the other uses it
line 10 depends on line 5: one declares a quoted identifier and the other has a body and comes after it
The more verbose output comes from the Nim compiler built with -d:nimDebugReorder (see #20888).
Nim Version
Nim Compiler Version 1.7.3 [Linux: amd64]
Compiled at 2022-11-21
Copyright (c) 2006-2022 by Andreas Rumpf
git hash: 370f1fd
active boot switches: -d:release
Current Standard Output Logs
No response
Expected Standard Output Logs
No response
Possible Solution
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
I ran into this issue, but in a different scenario:
{.experimental: "codeReordering".}
proc`a`() =b()
procb() =discard# Warning: Circular dependency detected. `codeReordering` pragma may not be able to reorder some nodes properly
What happened?
See this code.
I am receiving a warning under the conditions mentioned in the comments:
The more verbose output comes from the Nim compiler built with -d:nimDebugReorder (see #20888).
Nim Version
Nim Compiler Version 1.7.3 [Linux: amd64]
Compiled at 2022-11-21
Copyright (c) 2006-2022 by Andreas Rumpf
git hash: 370f1fd
active boot switches: -d:release
Current Standard Output Logs
No response
Expected Standard Output Logs
No response
Possible Solution
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: