Fix issue 20589 - typeof may give wrong result in case of classes defining opCall operator

[drug007]

See bugzilla here

[dlang-bot]

Thanks for your pull request and interest in making D better, @drug007! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

• My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
• My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
• I have provided a detailed rationale explaining my changes
• New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.

---

If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Auto-close	Bugzilla	Severity	Description
✓	20589	normal	typeof may give wrong result in case of classes defining opCall operator

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub fetch digger
dub run digger -- build "master + phobos#7398"

[drug007]

@wilzbach could you point out where can I add a test for this issue?

[thewilsonator]

Please change the commit message to say Fix issue 20589.

[Geod24]

Please change the commit message to say Fix issue 20589.

Fix issue 20589 - <Issue title>

People watching the core repositories don't want to open every single notification they get, just those that seems relevant to their area of expertise. Likewise, when going through old PR / commits (trying to find where a bug was fixed, regression introduced, or feature added), it is extremely painful to see commit without correct title / description.

[Geod24]

Thanks for changing the title, but the bot picks up the commit, so you also have to go and edit it.