-
-
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
regression from v1.6.12: --styleCheck:error
stops checking style for openArray
#24269
Comments
tersec
changed the title
regression from v.1.6.12:
regression from v1.6.12: Oct 9, 2024
--styleCheck:error
stops checking style for openArray
--styleCheck:error
stops checking style for openArray
Knew about this but forgot, this is a regression from #20095, it applies to any symbol from the standard library. The issue is in the lines that do |
metagn
added a commit
to metagn/Nim
that referenced
this issue
Oct 10, 2024
This was referenced Oct 10, 2024
Had to open PRs to packages to fix:
|
These have both been merged. |
narimiran
pushed a commit
that referenced
this issue
Oct 11, 2024
fixes #24269, refs #20095 Instead of checking the package of the *used sym* to determine whether a stylecheck should trigger, we check the package of the lineinfo instead. Before #20095 this checked for the current compilation context module instead which caused issues with generic procs, but the lineinfo should more closely match the AST. I figured this might cause issues with includes etc but the foreign package test specifically tests for an include and passes, so maybe the package determining logic accounts for this already. This still might not be the correct logic, I'm not too familiar with the package handling in the compiler. Package PRs, both merged: - json_rpc: status-im/nim-json-rpc#226 - json_serialization: status-im/nim-json-serialization#99 (cherry picked from commit aaf6c40)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Using
nim c -c --styleCheck:error r
Nim Version
Produces error:
Does not produce error:
Current Output
Expected Output
Known Workarounds
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: