opEquals was made auto so it appeared in the now defunct generated .di file. #2190
Conversation
Thanks for your pull request, @schveiguy! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub fetch digger
dub run digger -- build "stable + druntime#2190" |
It seems like it was changed to |
According to git-blame it was me who changed that. I don't remember what the exact reason was, but I suspect that was to keep the .d file in sync with the .di file which was manually edited back then. Now that we actually only copy object.d to the import folder, that should be unnecessary now. Please note that there is a second |
Yes. At some point in the past, object_.d and object.di were two separate files that were manually synchronized. In other words, whenever you added something to object_.d, you had to add it to object.di. In PR #1222, this was migrated to generating object.di from object_.d, which in case of this function, would REMOVE the function declaration completely (I think). Fast forward to today, we have no object.di file, we have no reason to keep this as auto. Not a big deal, except the docs show it as returning auto, when it returns a bool (and should be listed this way). |
drat, didn't notice that. Will update. |
eec79ba
to
9896d73
Compare
Updated, now got both of them. |
I still only see one. |
Same here. |
9896d73
to
d1299e3
Compare
Sorry, I'm learning new git techniques 😆. Should be fixed now. |
See 8ff270c
This makes the ddoc generation return auto, but it should really specify the return type. There's also no reason to semantic the function every compilation to figure this out.