Fix Issue 20760 - checkaction=context doesnt print floating point num…

[MoonlightSentinel]

…bers correctly

This fixes most issues allthough casting from real to c_long_double might be
problematic for platforms where D's real uses 80 bits but C's long double is
only 64 bit wide (e.g. Win64).

Note that this might cause some deprecations because of https://issues.dlang.org/show_bug.cgi?id=20759

[dlang-bot]

Thanks for your pull request and interest in making D better, @MoonlightSentinel! 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
✓	20760	normal	checkaction=context doesnt print floating point numbers correctly

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

[schveiguy]

Shouldn't R be a C type? I didn't think that C supported imaginary D types.

[MoonlightSentinel]

Casting to a non-imaginary type yields 0, e.g.

ireal num = 2i;
writeln(cast(double) num);    // 0
writeln(cast(idouble) num);   // 2i

But ireal is stored the same way as real IIRC.

[schveiguy]

OK, I see what the point of this is then. I was thinking the issue was that C wasn't properly using the types because of the imaginariness.

One last thing: put a static assert that V is ireal. It shouldn't affect compilation time at all, and ensures some weird problem doesn't creep in here.

[MoonlightSentinel]

Done

[schveiguy]

OK, I see what the point of this is then. I was thinking the issue was that C wasn't properly using the types because of the imaginariness.

One last thing: put a static assert that V is ireal. It shouldn't affect compilation time at all, and ensures some weird problem doesn't creep in here.