It's fixed already. But I searched at the wrong place. The
compiler is too huge for me. o.O
On Monday, January 28, 2013 11:16:26 Namespace wrote:
> > And that prevents a workaround for the missing auto ref. :o)
> > It seems dmd 2.060 is far more useable than 2.061 (for users
> > which use structs, of course).
> > I will switch back.
>
> I'm still interested in this problem. But how can I
And that prevents a workaround for the missing auto ref. :o)
It seems dmd 2.060 is far more useable than 2.061 (for users
which use structs, of course).
I will switch back.
I'm still interested in this problem. But how can I identify the
specific compiler code where this error comes from?
I k
On Sunday, 27 January 2013 at 23:05:16 UTC, Jonathan M Davis
wrote:
On Sunday, January 27, 2013 12:42:28 Dicebot wrote:
Looks like a bug in function overload selection.
Definitely.
- Jonathan M Davis
And that prevents a workaround for the missing auto ref. :o)
It seems dmd 2.060 is far more
On Sunday, January 27, 2013 12:42:28 Dicebot wrote:
> Looks like a bug in function overload selection.
Definitely.
- Jonathan M Davis
Ok, I will open a bug report for this.
Same with this code: http://dpaste.1azy.net/2c98fe95
But there I found no workaround.
This works: new C(cast(A) new B(), FloatRect(0, 1, 2, 3));
But that is ugly. o.O
I think you are right and it is a bug in function overload
selection. :(
On Sunday, 27 January 2013 at 11:42:29 UTC, Dicebot wrote:
Looks like a bug in function overload selection.
I hope not!
That would be really bad. That is part of my solution as long as
auto ref isn't there. :D
Looks like a bug in function overload selection.
The following code prints:
/home/c494/c719.d(27): Error: (Vec2!(float) __ctmp1173 =
_D4c71911__T4Vec2TfZ4Vec26__initZ;
, __ctmp1173).this(4F, 2F) is not an lvalue
[code]
import std.stdio;
struct Vec2(T) {
public:
T x;
T y;
this(T x, T y) {
}
}
10 matches
Mail list logo
