On Tue, 28 Jul 2015 02:16:56 +
lobo swampl...@gmail.com wrote:
Hi all,
I have a bunch of unittests for template code taking any numeric
type. Because I'm lazy I just use the approxEqual for both
floating point and integer comparisons in these tests.
In DMD 2067.1 everthing
On Tuesday, 28 July 2015 at 07:42:32 UTC, Daniel Kozák wrote:
Even if this will be considered as non compiler bug, it is a
regression on phobos side and should be addressed. So please
fill a bug report on http://issues.dlang.org
done,
thanks
https://issues.dlang.org/show_bug.cgi?id=14842
On Tue, 28 Jul 2015 08:50:53 +0200
Daniel Kozák ko...@dlang.cz wrote:
On Tue, 28 Jul 2015 02:16:56 +
lobo swampl...@gmail.com wrote:
I would say it is a compiler bug.
consider this:
bool some(real x, real y) {
return true;
}
bool some(float x, float y) {
return
On Tue, 28 Jul 2015 02:16:56 +
lobo swampl...@gmail.com wrote:
Hi all,
I have a bunch of unittests for template code taking any numeric
type. Because I'm lazy I just use the approxEqual for both
floating point and integer comparisons in these tests.
In DMD 2067.1 everthing
Hi all,
I have a bunch of unittests for template code taking any numeric
type. Because I'm lazy I just use the approxEqual for both
floating point and integer comparisons in these tests.
In DMD 2067.1 everthing compiled OK but in 2068-b2 I get the
errors shown at the end of this post for
