Fix Issue 21246 - Compiler must show mismatching types when functions do not properly override

[RazvanN7]

When the overriding function has the same name as a potential overriden function, then print the fully qualified names of the parameters of the overriden function.

[dlang-bot]

Thanks for your pull request and interest in making D better, @RazvanN7! 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
✓	21246	normal	Compiler must show mismatching types when functions do not properly override

Testing this PR locally

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

dub run digger -- build "master + dmd#11734"

[Geod24]

Those both return pointers... So we're just comparing the pointers ?

[RazvanN7]

Hmm.. I was under the impression that was changed to return a slice.

[Geod24]

You wouldn't be able to call it in printf and error if that was the case ;)

[Geod24]

Reading the description, it looks like the check should have been based on ident and not toChars.

[AndrejMitrovic]

It would be better if it compared the two parameter symbol names, and if they are the same (but different types) then explicitly mention that in the diagnostic.

I'm afraid the diagnostics would otherwise become too verbose..