Fix 24056 - const uninitialized data at module scope is not in TLS

[dkorpel]

No description provided.

[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
✓	24056	normal	const uninitialized data at module scope is not in TLS

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

[AndrejMitrovic]

I thought it would make more sense to move const data to TLS. Only immutable is documented as shared by the spec as far as I know. @WalterBright what do you think about https://issues.dlang.org/show_bug.cgi?id=24056?

[dkorpel]

I thought it would make more sense to move const data to TLS.

That would break or subtly change the behavior of existing code.

[RazvanN7]

Please add a changelog entry.

[dkorpel]

For a bug fix?

[RazvanN7]

For a deprecation. Code that used to compile will now issue a deprecation.