Unum II announcement

[Andrei Alexandrescu via Digitalmars-d]

On 9/24/16 10:22 PM, Nick B wrote:
> I suggest that now, programmers would/may have a choice: be slow and
> correct, or fast and incorrect, and that would depend if real accuracy
> is important or not, the types of problems being work on, and cost of
> failure.

Let me just say it doesn't seem our policy of "slow but correct" has 
bore fruit, and I think it's time to dispense with it. There are methods 
to improve correctness through algorithmic means, but slow primitives 
you're stuck with. -- Andrei