Fix 23295 - explain why scope inference failed

[dkorpel]

Following up #14368

I'm using an associative array instead of an extra field to VarDeclaration to reduce memory. It is annoying that there's no easy way to find the corresponding VarDeclaration of a Parameter, so I'll pass it into checkParamArgumentEscape.

So far it only works for direct @safe errors, and not for a stored AttributeViolation (#13957), which is a future improvement..

[dlang-bot]

Thanks for your pull request and interest in making D better, @dkorpel! 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
✓	23295	enhancement	[dip1000] explain why scope inference failed

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#14373"

[dkorpel]

@Geod24 We briefly discussed this in London after the foundation meeting.

[RazvanN7]

Is there really any point in having both these functions? Can't we have just the deinitalize one and skip calling initialize? If not, can't we give it a more generic name like reset ?

[dkorpel]

I made it consistent with the other aggregates in initDMD and deinitializeDMD.

[dkorpel]

It's now a single reset function