Visual D debugging messed up

[Rainer Schuetze]

On 23/05/2018 22:46, IntegratedDimensions wrote:
> Another issues is that the watch/auto's are arounding doubles.
> 
> I have a value that is like 4.999953943 and it shows 5.
> 
> I'd rather see at least several digits. This is because when I cast it 
> to int I get 4 and the original shows 5 and it is confusing where the 1 
> went when one expects to see higher precision... there is plenty of 
> rooms to show more digits so no reason to round... it is a double after 
> all but looks like an int in the watch window.

I could reproduce that with a slightly larger number of '9's. Agreed, it 
should not round. I've changed that to always show the full number of 
digits relevant for the type (float/double/real).