[Issue 13469] x^^y wrong result

2017-12-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13469 Iain Buclaw changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 13469] x^^y wrong result

2014-09-18 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13469 Илья Ярошенко ilyayaroshe...@gmail.com changed: What|Removed |Added Keywords||wrong-code --

[Issue 13469] x^^y wrong result

2014-09-18 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13469 --- Comment #1 from Don clugd...@yahoo.com.au --- Are you sure this isn't just the difference in precision between double and real? The compile time values are done at 80 bit precision. The runtime pow() is done with 64 bit floats. --

[Issue 13469] x^^y wrong result

2014-09-18 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13469 --- Comment #2 from Илья Ярошенко ilyayaroshe...@gmail.com --- You are right! Any way CTFE^^ and Runtime^^ should be identical between each other and std.math pow. import std.math; static assert(1.7^^1000 == double(1.7).pow(1000));//OK void main()