Bug 18464 – fullyQualifiedName!ifloat and fullyQualifiedName!cfloat fail
Status
RESOLVED
Resolution
WONTFIX
Severity
enhancement
Priority
P1
Component
phobos
Product
D
Version
D2
Platform
x86
OS
Windows
Creation time
2018-02-19T05:00:18Z
Last change time
2021-02-07T13:34:25Z
Assigned to
No Owner
Creator
katemmons0
Comments
Comment #0 by katemmons0 — 2018-02-19T05:00:18Z
fullyQualifiedName does not work on any of the i or c variants of float, double, and real.
static assert(!__traits(compiles, fullyQualifiedName!ifloat));
static assert(!__traits(compiles, fullyQualifiedName!idouble));
static assert(!__traits(compiles, fullyQualifiedName!ireal));
static assert(!__traits(compiles, fullyQualifiedName!cfloat));
static assert(!__traits(compiles, fullyQualifiedName!cdouble));
static assert(!__traits(compiles, fullyQualifiedName!creal));
Comment #1 by greensunny12 — 2018-02-19T05:12:58Z
While not directly related to your issue, but are you aware that the i and c variants are about to be deprecated? (they have been deprecated in 2012, but -transition=complex has never been activated by default)
Comment #2 by katemmons0 — 2018-02-21T03:13:30Z
(In reply to Seb from comment #1)
> While not directly related to your issue, but are you aware that the i and c
> variants are about to be deprecated? (they have been deprecated in 2012, but
> -transition=complex has never been activated by default)
Nope, didn't know that. I don't need this for anything, I just noticed it and thought I would report it. https://imgur.com/gallery/cMfkFGP
Comment #3 by tiberiulepadatu14 — 2018-10-21T17:47:25Z
I think that the error comes from the fact that fqnType does not recognize c and i types. Should I write a fix, giving the fact that the types will be eliminated?
Comment #4 by bugzilla — 2021-02-07T13:34:25Z
With the deprecation of complex native types, I think, this is a WONTFIX.