[Issue 14453] segfault in release mode

https://issues.dlang.org/show_bug.cgi?id=14453 drug007 changed: What|Removed |Added CC||drug2...@bk.ru --- Comment #1 from drug007 --- dm

[Issue 13920] DMD crash when trying to set a delegate from __traits(getOverloads)

https://issues.dlang.org/show_bug.cgi?id=13920 --- Comment #4 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/c8173f3a87a14312f734f584af80fa686b4333f3 fix Issue 13920 - DMD crash

[Issue 14453] New: segfault in release mode

https://issues.dlang.org/show_bug.cgi?id=14453 Issue ID: 14453 Summary: segfault in release mode Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement Priority: P1

[Issue 14451] static-foreach uses huge stack for no reason

https://issues.dlang.org/show_bug.cgi?id=14451 --- Comment #3 from yebblies --- (In reply to Tomer Filiba from comment #2) > couldn't inner-scopes be rewritten like that, only making sure the lambda is > fully-scoped so that external variables will be heap-allocated That is automatic outlining,

[Issue 10943] Nested lambda alias in template arguments has no code generated

https://issues.dlang.org/show_bug.cgi?id=10943 Justin Whear changed: What|Removed |Added CC||jus...@economicmodeling.com --- Comment #1 fr

[Issue 14452] [REG2.067] Floating point invalid operation when returning a structure containing a float field

https://issues.dlang.org/show_bug.cgi?id=14452 Martin Krejcirik changed: What|Removed |Added CC||m...@krej.cz Summary|Floating

[Issue 14452] Floating point invalid operation when returning a structure containing a float field

https://issues.dlang.org/show_bug.cgi?id=14452 Răzvan Ștefănescu changed: What|Removed |Added Keywords||wrong-code --- Comment #1 from Răzvan Șt

[Issue 14452] New: Floating point invalid operation when returning a structure containing a float field

https://issues.dlang.org/show_bug.cgi?id=14452 Issue ID: 14452 Summary: Floating point invalid operation when returning a structure containing a float field Product: D Version: unspecified Hardware: x86 OS: Wi

[Issue 14340] AssertError in std.algorithm.sorting: unstable sort fails to sort an array with a custom predicate

https://issues.dlang.org/show_bug.cgi?id=14340 Ivan Kazmenko changed: What|Removed |Added Keywords||pull --- Comment #2 from Ivan Kazmenko ---

[Issue 14451] static-foreach uses huge stack for no reason

https://issues.dlang.org/show_bug.cgi?id=14451 --- Comment #2 from Tomer Filiba --- you are correct: === void foo() { { ulong[32] x; writeln(x.ptr); } { ulong[32] x; writeln(x.ptr); } { ulong[32] x; writeln(x.ptr

[Issue 14451] static-foreach uses huge stack for no reason

https://issues.dlang.org/show_bug.cgi?id=14451 yebblies changed: What|Removed |Added CC||yebbl...@gmail.com Hardware|x86_64

[Issue 14436] Optimizer fails to remove comparison loop when comparing array against null

https://issues.dlang.org/show_bug.cgi?id=14436 --- Comment #6 from yebblies --- Ok, I'll have a look. This can probably be special-cased, although there is a long-standing problem that the optimizer doesn't look at constant data correctly. --

[Issue 14451] static-foreach uses huge stack for no reason

https://issues.dlang.org/show_bug.cgi?id=14451 Tomer Filiba changed: What|Removed |Added CC||tomerfil...@gmail.com --

[Issue 14451] New: static-foreach uses huge stack for no reason

https://issues.dlang.org/show_bug.cgi?id=14451 Issue ID: 14451 Summary: static-foreach uses huge stack for no reason Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: major Pr

[Issue 5329] Simple logging facility in the stdlib

https://issues.dlang.org/show_bug.cgi?id=5329 Robert Schadek changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 14436] Optimizer fails to remove comparison loop when comparing array against null

https://issues.dlang.org/show_bug.cgi?id=14436 --- Comment #5 from Marc Schütz --- (In reply to yebblies from comment #4) > By empty array do you mean empty array literal? > > eg assert(x != []); Yes, it should read "empty array [literal] or string literal". In fact, the code generated for `in