Fix issue 23000 - final switch error has no line number with -checkaction=C

[dkorpel]

The assert(0) for the default case of the final switch is generated in statementsem.d:

s = new ExpStatement(ss.loc, new AssertExp(ss.loc, IntegerExp.literal!0));

Then in e2ir.d, the location of the assert expression is used, which is IntegerExp.literal!0 in this case, which doesn't have a location set. This patch makes it use the location of the statement instead, which is actually consistent with the other checkactions since a D assert also uses the location of the statement.

I tested this manually, but not sure how to add this to the test suite because I can't catch a C assert, and I'm not sure we even want a new runnable test for something trivial like this, but I'm open to suggestions.

[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
✓	23000	normal	final switch error has no line number with -checkaction=C

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

[thewilsonator]

Is is possible to write a test case for this?

[dkorpel]

Is is possible to write a test case for this?

I tested this manually, but not sure how to add this to the test suite because I can't catch a C assert, and I'm not sure we even want a new runnable test for something trivial like this, but I'm open to suggestions.