[Issue 15939] GC.collect causes deadlock in multi-threaded environment

https://issues.dlang.org/show_bug.cgi?id=15939 --- Comment #24 from Aleksei Preobrazhenskii --- (In reply to Martin Nowak from comment #23) > Anyone still experiencing this issue? Can't seem to fix it w/o reproducing > it. Since I changed signals to real-time and

[Issue 16526] @safe code should do null check for members when appropriate

https://issues.dlang.org/show_bug.cgi?id=16526 --- Comment #3 from Steven Schveighoffer --- (In reply to Sobirari Muhomori from comment #1) > struct S > { > byte[3000] a,b; > } > void f(ref S s) > { > g(s.b); > } Actually, technically this could trigger a check

[Issue 16526] @safe code should do null check for members when appropriate

https://issues.dlang.org/show_bug.cgi?id=16526 --- Comment #2 from Steven Schveighoffer --- Yes, this is what I meant by "There are still ways to access data beyond one page without incurring a check with this scheme, but we are talking about very weird and rare code." --

[Issue 14251] synchronized (mtx) doesn't check attributes (pure, const)

https://issues.dlang.org/show_bug.cgi?id=14251 --- Comment #22 from Andrei Alexandrescu --- (In reply to Martin Nowak from comment #21) > Forcing everyone to use the same attributes is too limiting/breaks code, > let's replace the old C API w/ templated library code.

[Issue 14251] synchronized (mtx) doesn't check attributes (pure, const)

https://issues.dlang.org/show_bug.cgi?id=14251 --- Comment #21 from Martin Nowak --- (In reply to Andrei Alexandrescu from comment #19) > > Just look at core.sync, none of the methods can be implemented const or > > pure, still they get called from const/pure code. > > That's not

[Issue 16526] @safe code should do null check for members when appropriate

https://issues.dlang.org/show_bug.cgi?id=16526 Sobirari Muhomori changed: What|Removed |Added Hardware|x86 |All

[Issue 16499] Misleading error message for 'in' operator with wrong argument

https://issues.dlang.org/show_bug.cgi?id=16499 Sobirari Muhomori changed: What|Removed |Added Keywords||diagnostic

[Issue 16405] Trojan Win32/Ipac.B!cl detected on dmd-2.071.1.exe

https://issues.dlang.org/show_bug.cgi?id=16405 --- Comment #7 from Sobirari Muhomori --- I uploaded only ddemangle.exe --

[Issue 16526] New: @safe code should do null check for members when appropriate

https://issues.dlang.org/show_bug.cgi?id=16526 Issue ID: 16526 Summary: @safe code should do null check for members when appropriate Product: D Version: D2 Hardware: x86 OS: Mac OS X Status: NEW

[Issue 16342] std.algorithm.fill can't fill a char[]?

https://issues.dlang.org/show_bug.cgi?id=16342 niklas.vo...@gmail.com changed: What|Removed |Added CC||niklas.vo...@gmail.com --- Comment

[Issue 16525] New: C++ member variables have no mangling

https://issues.dlang.org/show_bug.cgi?id=16525 Issue ID: 16525 Summary: C++ member variables have no mangling Product: D Version: D2 Hardware: All OS: Linux Status: NEW Keywords: ice Severity:

[Issue 15939] GC.collect causes deadlock in multi-threaded environment

https://issues.dlang.org/show_bug.cgi?id=15939 --- Comment #23 from Martin Nowak --- Anyone still experiencing this issue? Can't seem to fix it w/o reproducing it. --