yebblies <> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
                 CC|                            |
         Resolution|WONTFIX                     |

--- Comment #15 from yebblies <> 2012-02-01 14:14:35 EST ---
I actually think this is something worth asking for.
I intend to have a go at implementing cent and ucent once I understand more of
the backend code, so it hopefully isn't too far off.

The following code gives _parsing_ errors, which doesn't make a lot of sense.

version(none) cent x;
static if (is(cent)) {}
static if (__traits(compiles, { cent x; }))

If this was like macro, and we didn't know what cent/ucent support might
eventually look like, then it would make sense to reject it that early.  But we
know cent/ucent will behave exactly like the rest of the built in integer

The solution is trivial:

Please take a look and tell me what we lose by adding this to the language.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to