[Issue 19014] Compiler imports symbols that aren't actually imported.

https://issues.dlang.org/show_bug.cgi?id=19014 Steven Schveighoffer changed: What|Removed |Added CC||schvei...@yahoo.com --- Comment #1

[Issue 19014] New: Compiler imports symbols that aren't actually imported.

https://issues.dlang.org/show_bug.cgi?id=19014 Issue ID: 19014 Summary: Compiler imports symbols that aren't actually imported. Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 19013] New: Allocation of array that has indirections makes incorrect assumption about zeroing

https://issues.dlang.org/show_bug.cgi?id=19013 Issue ID: 19013 Summary: Allocation of array that has indirections makes incorrect assumption about zeroing Product: D Version: D2 Hardware: All OS: All

[Issue 18984] Debugging stack struct's which are returned causes incorrect debuginfo.

https://issues.dlang.org/show_bug.cgi?id=18984 --- Comment #6 from Manu --- > but I have not been able to > get RVO from C++ to see what happens there. I think if you build with C++14 (RVO guaranteed) and std::move the result to return value you should be able to force it. Copy elision is all

[Issue 19009] core.internal.hash.hashOf default hash (absent `toHash`) should be `@nogc`

https://issues.dlang.org/show_bug.cgi?id=19009 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/4f5b049559d69c9c696c6534302ecbcff30126d5 Fix Issue 19009 - core.internal.hash.hashOf default

[Issue 19009] core.internal.hash.hashOf default hash (absent `toHash`) should be `@nogc`

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

[Issue 19012] New: `scoped` crashes when instantiating an object with `alias this`

https://issues.dlang.org/show_bug.cgi?id=19012 Issue ID: 19012 Summary: `scoped` crashes when instantiating an object with `alias this` Product: D Version: D2 Hardware: x86_64 OS: Linux Status:

[Issue 19010] new fails on dynamic array aliases

https://issues.dlang.org/show_bug.cgi?id=19010 Basile B. changed: What|Removed |Added CC||b2.t...@gmx.com --- Comment #2 from Basile B.

[Issue 19010] new fails on dynamic array aliases

https://issues.dlang.org/show_bug.cgi?id=19010 ag0aep6g changed: What|Removed |Added CC||ag0ae...@gmail.com --- Comment #1 from ag0aep6g

[Issue 12444] std.array uninitializedArray & minimallyInitializedArray missing APPENDABLE attribute / capacity info

https://issues.dlang.org/show_bug.cgi?id=12444 Steven Schveighoffer changed: What|Removed |Added Status|REOPENED|RESOLVED CC|

[Issue 18995] std.array.array doesn't free elements

https://issues.dlang.org/show_bug.cgi?id=18995 Steven Schveighoffer changed: What|Removed |Added CC||safety0ff.b...@gmail.com --- Comment

[Issue 18439] Error: cannot use operator ~= in @nogc delegate 'main.test.__lambda1'

https://issues.dlang.org/show_bug.cgi?id=18439 David Bennett changed: What|Removed |Added CC||davidbenn...@bravevision.co

[Issue 18985] bad error message for += operation on shared Object

https://issues.dlang.org/show_bug.cgi?id=18985 --- Comment #6 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/ff23072e11750a83da1078705a16f7d160e793d9 Fix Issue 18985 - bad error message for += operation on

[Issue 18985] bad error message for += operation on shared Object

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

[Issue 18984] Debugging stack struct's which are returned causes incorrect debuginfo.

https://issues.dlang.org/show_bug.cgi?id=18984 --- Comment #5 from Rainer Schuetze --- > This is closed right? IIRC fixes to stable no longer cause automatic closing. This is done when it is merged back to master to avoid spamming bugzilla with multiple messages. I think the patch can still be