Appender and CTFE
Kevin Bealer
kevindangerbealer at removedanger.gmail.com
Fri Mar 4 00:51:10 PST 2011
== Quote from Andrei Alexandrescu (SeeWebsiteForEmail at erdani.org)'s article
> I see nothing wrong with the occasional forking conditioned by __ctfe.
> Even today, code may fork an optimized but nonportable implementation of
> some algorithm. The main requirement is that such forks are rare enough
> to not cause undue maintenance burden.
>
> Andrei
Regarding maintenance burden, it should be easy to test the correctness of
such code:
in a unit test:
enum a = f(...);
assert(a == f(...));
Kevin
More information about the Digitalmars-d
mailing list