On Tuesday, 10 May 2016 at 22:17:00 UTC, pineapple wrote:
On Tuesday, 10 May 2016 at 09:57:11 UTC, pineapple wrote:
On Monday, 9 May 2016 at 18:56:15 UTC, Peter Häggman wrote:
No problem here (tested with everything in a single module).
I can't help more.
Front end version ?
Well, this is th
On Tuesday, 10 May 2016 at 09:57:11 UTC, pineapple wrote:
On Monday, 9 May 2016 at 18:56:15 UTC, Peter Häggman wrote:
No problem here (tested with everything in a single module). I
can't help more.
Front end version ?
Well, this is the full struct that has those malfeasant
overrides: http://
On Monday, 9 May 2016 at 18:56:15 UTC, Peter Häggman wrote:
No problem here (tested with everything in a single module). I
can't help more.
Front end version ?
Well, this is the full struct that has those malfeasant
overrides: http://pastebin.com/9h2s028J
On Monday, 9 May 2016 at 11:22:37 UTC, pineapple wrote:
On Monday, 9 May 2016 at 00:27:17 UTC, Peter Häggman wrote:
Can you show your GLColor struct ? Maybe it contains an alias
this or something else that mess the overload resolution.
My GLColor struct: http://pastebin.com/mUcA6G85
No probl
On Monday, 9 May 2016 at 00:27:17 UTC, Peter Häggman wrote:
Can you show your GLColor struct ? Maybe it contains an alias
this or something else that mess the overload resolution.
My GLColor struct: http://pastebin.com/mUcA6G85
On Sunday, 8 May 2016 at 13:28:47 UTC, pineapple wrote:
[...]
I get a compiler error like so:
E:\Dropbox\Projects\d\mach\sdl\surface.d(434): Error: none
of the overloads of 'opIndexAssign' are callable using argument
types (GLColor!float, int, int), candidates are:
E:\Dropbox\Projects\
In my struct I have some methods with these signatures:
void opIndexAssign(T)(in GLColor!T color, in int x, in int y)
void opIndexAssign(T1, T2)(in GLColor!T1 color, in Vector2!T2
vector)
void opIndexAssign(in uint value, in int x, in int y)
And when I try to do this:
thing[2,
