-
-
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
explicitly import using std/
in tempfiles.nim
#22851
Conversation
Thanks for your hard work on this PR! Hint: mm: orc; opt: speed; options: -d:release |
It's been most of a decade since So, this PR reminds me to ask - is there any reason to not just change all stdlib internal imports to |
It was rejected before. I suppose we can make a warning, which is disabled by default, that is enforced for the compiler or stdlib. |
Hmm. I could not find any discussion besides #8024 , It's a bit hard to search for To be clear, all I was talking about was that inside the stdlib, all the imports are consistently just It might also make sense in the test programs. (Also, I didn't mean to over-volunteer anyone for this. If there is receptiveness, I could do all the edits.. it mostly seems like just a lot of text edits.) |
@ringabout feel free to work on it. |
Sure thing |
At least on modern Nim
tempfiles
is not usable if the user has https://github.com/oprypin/nim-random installed, because the compiler picks the nimble path over the stdlib path (apparently).