Thanks Adam, that cleared it up for me.
I've been experimenting with the -betterC switch and stumbled
upon something that didn't quite make sense to me.
I've put together a small example [1] of Win32 code with a window
callback that has to be nothrow as per the definition of WNDPROC
somewhere in core.sys.windows. However, calling
I'm not sure whether I've found a bug or if I found some very
strange but intended behavior. If it is indeed intended behavior,
I'd like to know the rationale behind it because this one
surprised me a lot when I found it out after 16+ hours of
debugging...
Have a look at this code snippet:
Hi there,
I was wondering why I should ever prefer std.range.lockstep over
std.range.zip. In my (very limited) tests std.range.zip offered
the same functionality as std.range.lockstep, i.e. I was able to
iterate using `foreach(key, value; std.range.zip(...)) {}` which,
according to the docs,
