Fix Issue 21110 - OOB memory access, safety violation

[RazvanN7]

It seems that this PR [1] forgot to add checks for OOB accesses. I had to modify _d_assert_fail to be able to put a nice error message.

[1] #1891

[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
✓	21110	regression	OOB memory access, safety violation

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 "stable + druntime#3267"

[thewilsonator]

Please target stable

[Geod24]

Test seems to be failing on all platforms

[RazvanN7]

@Geod24 @thewilsonator This seems to be green now. Could you please take another look?

[thewilsonator]

This still targets master.

[RazvanN7]

It'a an old regression. Since 2.065.

[RazvanN7]

Of course now we have spurious error messages :((