[Issue 14246] RAII - proper destruction of partially constructed objects/structs

https://issues.dlang.org/show_bug.cgi?id=14246 --- Comment #8 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/1e755c648e5142719d50dcf984f10ace5b8f8357 fix Issue 14246 - RAII - proper destruction of partially

[Issue 17489] ICE in ddmd/argtypes.d

https://issues.dlang.org/show_bug.cgi?id=17489 --- Comment #2 from greensunn...@gmail.com --- It seems that argtypemerge has troubles when confronted with an error: /home/seb/dlang/dmd/generated/linux/debug/64/../../../../../phobos/std/traits.d(1046,60): Error: parameter index must be in range

[Issue 17489] ICE in ddmd/argtypes.d

https://issues.dlang.org/show_bug.cgi?id=17489 --- Comment #1 from greensunn...@gmail.com --- It seems that argtypemerge has troubles when confronted with an error: /home/seb/dlang/dmd/generated/linux/debug/64/../../../../../phobos/std/traits.d(1046,60): Error: parameter index must be in range

[Issue 17489] New: ICE in ddmd/argtypes.d

https://issues.dlang.org/show_bug.cgi?id=17489 Issue ID: 17489 Summary: ICE in ddmd/argtypes.d Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: major Priority: P1

[Issue 16108] `to!string` fails on struct with disabled postblit

https://issues.dlang.org/show_bug.cgi?id=16108 --- Comment #6 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/3d80936f0b1e56418d6826180a7a9dbb29e01b7f Fix Issue 16108: tostrings fails on struct with

[Issue 17488] Platform-inconsistent behavior from getTempDir()

https://issues.dlang.org/show_bug.cgi?id=17488 Vladimir Panteleev changed: What|Removed |Added CC|

[Issue 17399] [REG2.071] core.checkedint.addu cannot inline function

https://issues.dlang.org/show_bug.cgi?id=17399 Martin Krejcirik changed: What|Removed |Added Summary|core.checkedint.addu cannot |[REG2.071]

[Issue 16538] Parameter head-const-ness shouldn't matter but does

https://issues.dlang.org/show_bug.cgi?id=16538 --- Comment #2 from Walter Bright --- Fixed by https://github.com/dlang/dmd/pull/6731 --

[Issue 16600] Wrong error message for ambiguous mutable/immutable constructor

https://issues.dlang.org/show_bug.cgi?id=16600 Walter Bright changed: What|Removed |Added Status|REOPENED|RESOLVED

[Issue 16303] covariant delegates should implicitly convert

https://issues.dlang.org/show_bug.cgi?id=16303 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 17407] [REG2.067] __traits(compiles) triggers assertion failure

https://issues.dlang.org/show_bug.cgi?id=17407 Martin Krejcirik changed: What|Removed |Added Summary|[REG] __traits(compiles)|[REG2.067]

[Issue 17354] An overload in a final class can silently hide base methods

https://issues.dlang.org/show_bug.cgi?id=17354 b2.t...@gmx.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 17349] Covariant overrides should be allowed

https://issues.dlang.org/show_bug.cgi?id=17349 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 17349] Covariant overrides should be allowed

https://issues.dlang.org/show_bug.cgi?id=17349 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/832031adddadc3b9b8a3bca94bd30be1393b570a fix Issue 17349 - Covariant overrides should be allowed

[Issue 4559] Disallowing single semicolons

https://issues.dlang.org/show_bug.cgi?id=4559 Nemanja Boric <4bur...@gmail.com> changed: What|Removed |Added CC||4bur...@gmail.com ---

[Issue 4559] Disallowing single semicolons

https://issues.dlang.org/show_bug.cgi?id=4559 Stefan Koch changed: What|Removed |Added CC||uplink.co...@gmail.com

[Issue 4559] Disallowing single semicolons

https://issues.dlang.org/show_bug.cgi?id=4559 --- Comment #5 from Andrei Alexandrescu --- (In reply to uplink.coder from comment #4) > (In reply to Andrei Alexandrescu from comment #3) > > No need for a DIP, we should just convert this to an error. > > If we do this, then we

[Issue 17488] New: Platform-inconsistent behavior from getTempDir()

https://issues.dlang.org/show_bug.cgi?id=17488 Issue ID: 17488 Summary: Platform-inconsistent behavior from getTempDir() Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement

[Issue 17474] non-property being treated as a property

https://issues.dlang.org/show_bug.cgi?id=17474 --- Comment #9 from Vladimir Panteleev --- (In reply to Eyal from comment #8) > I don't see how a=b invoking a(b) when a isn't a @property is justifiable. Yep, that `writeln = "Hello, world!";` works is an infamous

[Issue 4559] Disallowing single semicolons

https://issues.dlang.org/show_bug.cgi?id=4559 uplink.co...@googlemail.com changed: What|Removed |Added CC||uplink.co...@googlemail.com ---

[Issue 4559] Disallowing single semicolons

https://issues.dlang.org/show_bug.cgi?id=4559 --- Comment #3 from Andrei Alexandrescu --- No need for a DIP, we should just convert this to an error. --

[Issue 4559] Disallowing single semicolons

https://issues.dlang.org/show_bug.cgi?id=4559 dl...@ryanjframe.com changed: What|Removed |Added CC||dl...@ryanjframe.com --- Comment #2

[Issue 17485] bringToFront and/or upperBound slow

https://issues.dlang.org/show_bug.cgi?id=17485 --- Comment #3 from Steven Schveighoffer --- Indeed, memmove fixes the specific use case: https://forums.dlang.org/post/ohgjec$1aar$1...@digitalmars.com However, I think we should do a full examination of everything C++ does

[Issue 17384] LDC x64 linker error in VS2017

https://issues.dlang.org/show_bug.cgi?id=17384 --- Comment #3 from ki...@gmx.net --- > Visual D doesn't use LDC's automatic detection because it doesn't allow > using different versions of VS. It is possible - via env variable `LDC_VSDIR`. For LDC 1.0.0 compatibility, it'd have to end with a

[Issue 4559] Disallowing single semicolons

https://issues.dlang.org/show_bug.cgi?id=4559 Infiltrator changed: What|Removed |Added CC||and...@erdani.com,

[Issue 4558] To spot a possible bug in code that doesn't change a value

https://issues.dlang.org/show_bug.cgi?id=4558 Infiltrator changed: What|Removed |Added CC|

[Issue 17486] lazy parameters can be used to hijack the pure system

https://issues.dlang.org/show_bug.cgi?id=17486 --- Comment #4 from Eyal --- The solution, clearly is to treat "lazy" is mere syntactic sugar to passing delegates - thus adding syntactic support for @nogc/etc attribute annotation on "lazy" parameters - and specifying their

[Issue 17474] non-property being treated as a property

https://issues.dlang.org/show_bug.cgi?id=17474 --- Comment #8 from Eyal --- Requiring @property on a for a=b to invoke a(b) sounds much more reasonable than the opposite. I don't see how a=b invoking a(b) when a isn't a @property is justifiable. --

[Issue 17474] non-property being treated as a property

https://issues.dlang.org/show_bug.cgi?id=17474 --- Comment #6 from Tomer Filiba (weka) --- (In reply to Walter Bright from comment #4) > But I can suggest avoiding using default function arguments. Default > arguments are a good solution for adding parameters without breaking >

[Issue 17474] non-property being treated as a property

https://issues.dlang.org/show_bug.cgi?id=17474 --- Comment #7 from Tomer Filiba (weka) --- (In reply to Stefan Koch from comment #5) > I am pretty sure the last thing you want is a function to be invoked as a > setter property if it returns an Lvalue. +1 --