-
-
Notifications
You must be signed in to change notification settings - Fork 5.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
a more earnest attempt at renaming Void #25162
Conversation
This is going to be massively conflict-prone, so I've separated it into the manual change to base/boot.jl which is fairly finicky and the automatic part that changes all the things. |
d20461c
to
418ed7c
Compare
Ok, the real deal this time. Can be easily rebased since the large rename step is scripted. |
418ed7c
to
eccd466
Compare
(Would you like a manual review here, or are you confident in your transformations? :)) |
I'm pretty sure this is correct, we just need to make a decision. |
What I recall from when we had |
If we have any other name ideas, it's pretty easy to change this since it's automated now. I still don't understand why |
There are very few cases where a value and its type have the same name except for case. There are several pairs, like |
There's an awful lot of support for this rename on the original issue – and a bit of dissent, but it's unusually lopsided. Perhaps people who voted up or down over there can chime in here? |
I concur with all arguments made in favor of the rename in the original issue and I want to add that Calling it |
I think |
I like terseness, so it's hard for me to support officially this rename, considering this evolution in length:
But if I'm honest, I must admit to secretely hope |
Ok, I'm not really set against this. The arguments for it are pretty reasonable. We should certainly have a shorter way to write |
eccd466
to
7cb77f0
Compare
Ready to go when CI passes. |
MacOS timeout; everything else has passed (again). |
For whatever it's worth, I was one of the few dissenters, and I admit that |
Crossposting the relevant bit I posted in support:
|
git ls-files base doc examples src stdlib test | xargs perl -i -ple '/\b(ccall|cglobal|cfunction)\b/ && s/\bVoid\b/Cvoid/g' git ls-files base doc examples src stdlib test | xargs perl -i -ple 's/\bPtr\{Void\}/Ptr{Cvoid}/g' git ls-files base doc examples src stdlib test | xargs perl -i -ple 's/\Ref\{Void\}/Ref{Cvoid}/g' perl -i -ple 's/\bVoid\b/Cvoid/g' base/atomics.jl base/libgit2/status.jl base/random/dSFMT.jl doc/src/manual/calling-c-and-fortran-code.md test/llvmcall.jl test/threads.jl git ls-files base doc examples src stdlib test | xargs perl -i -ple 's/\bVoid\b/Nothing/g'
7cb77f0
to
0f4d5db
Compare
I'd be in favor of making |
Let's see where there's more pain... Feel pain, apply syntax? |
FemtoCleaner is going to have it's work cut out for it :P |
Eh, this is a dead easy one to automate (as proved by the PR itself). |
It's also now available in Compat. |
Closes #25082.