While I consider going to a contest with tools you don't know yet
a very risky move, I can only empathize with some of the points
expressed by Manu.
We needed to mess with sc.ini for quite some time to get the
stars aligned
such that it would actually compile and find the linker+libs.
Same problem here, I used DMD-Win64 only once since I don't
remember the steps to get it to work (I think it involved
changing some .lib and path in sc.ini).
Debugging:
Poor debugging experience wastes your time every 5 minutes.
I can only speak for the Windows experience (since we failed to
get OSX
working); there are lots of problems with the debugging
experience under
visual studio...
I haven't logged bugs yet, but I intend to.
There were many instances of people wasting their time chasing
bugs in
random places when it was simply a case of the debugger lying
about the
value of variables to them, and many more cases where the
debugger simply
refused to produce values for some variables at all.
This happened to me several times, so that I end up relying on
writefln-debugging again. The fact that an IDE plugin exist at
all is a huge acceptance factor in the workplace.
