[Issue 12901] New: `in`/`out` contracts on struct constructor must require function body

https://issues.dlang.org/show_bug.cgi?id=12901 Issue ID: 12901 Summary: `in`/`out` contracts on struct constructor must require function body Product: D Version: D2 Hardware: All OS: All Status:

[Issue 12902] New: [ICE] Assertion failure '!ae-lengthVar' in 'expression.c' when using `opDollar`

https://issues.dlang.org/show_bug.cgi?id=12902 Issue ID: 12902 Summary: [ICE] Assertion failure '!ae-lengthVar' in 'expression.c' when using `opDollar` Product: D Version: D2 Hardware: All OS: All

[Issue 5555] [AA] Built-in associative arrays in pure nothrow functions

https://issues.dlang.org/show_bug.cgi?id= --- Comment #8 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/D-Programming-Language/druntime https://github.com/D-Programming-Language/druntime/commit/dd0f141f313fa6709939b4d626ff73296108ca70 Mark associative

[Issue 12900] REG 2.065: Wrong code in IfStatement condition Expression

https://issues.dlang.org/show_bug.cgi?id=12900 --- Comment #4 from Iain Buclaw ibuc...@gdcproject.org --- If there's a way to distinguish between different kinds of type in dmd's backend, you could throw in some tree checking. Such as: Assignments, left and right types are compatible.

[Issue 12904] New: Wrong-code for some slice to slice assignments when using `opDollar`

https://issues.dlang.org/show_bug.cgi?id=12904 Issue ID: 12904 Summary: Wrong-code for some slice to slice assignments when using `opDollar` Product: D Version: D2 Hardware: All OS: All Status:

[Issue 12903] New: dmd stuck forever in dmd TemplateInstance::toAlias()

https://issues.dlang.org/show_bug.cgi?id=12903 Issue ID: 12903 Summary: dmd stuck forever in dmd TemplateInstance::toAlias() Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity:

[Issue 12902] [ICE] Assertion failure '!ae-lengthVar' in 'expression.c' when using `opDollar`

https://issues.dlang.org/show_bug.cgi?id=12902 --- Comment #1 from Denis Shelomovskij verylonglogin@gmail.com --- Probably wrong-code regression Issue 12904 has the same root. --

[Issue 12905] New: [AA] `opCmp` in any struct allow other struct usage in associative array

https://issues.dlang.org/show_bug.cgi?id=12905 Issue ID: 12905 Summary: [AA] `opCmp` in any struct allow other struct usage in associative array Product: D Version: D2 Hardware: All OS: All

[Issue 12906] New: [CTFE] Static array of structs causes postblit call

https://issues.dlang.org/show_bug.cgi?id=12906 Issue ID: 12906 Summary: [CTFE] Static array of structs causes postblit call Product: D Version: D2 Hardware: All OS: All Status: NEW Keywords: CTFE,

[Issue 12907] New: [ICE] Assertion failure '0' in 'mangle.c' when using `auto` return type with lambda with dereferanced `function` call

https://issues.dlang.org/show_bug.cgi?id=12907 Issue ID: 12907 Summary: [ICE] Assertion failure '0' in 'mangle.c' when using `auto` return type with lambda with dereferanced `function` call Product: D Version: D2

[Issue 12908] New: [AA] `foreach` by keys and values over associative array in pure function allow impure function calls

https://issues.dlang.org/show_bug.cgi?id=12908 Issue ID: 12908 Summary: [AA] `foreach` by keys and values over associative array in pure function allow impure function calls Product: D Version: D2 Hardware: All

[Issue 12909] New: [AA] Function is incorrectly inferred as strongly pure for associative array with immutable array keys as argument

https://issues.dlang.org/show_bug.cgi?id=12909 Issue ID: 12909 Summary: [AA] Function is incorrectly inferred as strongly pure for associative array with immutable array keys as argument Product: D Version: D2

[Issue 5555] [AA] Built-in associative arrays in pure nothrow functions

https://issues.dlang.org/show_bug.cgi?id= --- Comment #9 from bearophile_h...@eml.cc --- I suggest to not close this issue until they are also @nogc. --

[Issue 12910] New: [AA] `rehash` is incorrectly inferred as strongly pure for some associative arrays

https://issues.dlang.org/show_bug.cgi?id=12910 Issue ID: 12910 Summary: [AA] `rehash` is incorrectly inferred as strongly pure for some associative arrays Product: D Version: D2 Hardware: All OS: All

[Issue 12910] [AA] `rehash` is incorrectly inferred as strongly pure for some associative arrays

https://issues.dlang.org/show_bug.cgi?id=12910 Denis Shelomovskij verylonglogin@gmail.com changed: What|Removed |Added Depends on||12909 --

[Issue 12909] [AA] Function is incorrectly inferred as strongly pure for associative array with key of non-mutable array or pointer as argument

https://issues.dlang.org/show_bug.cgi?id=12909 Denis Shelomovskij verylonglogin@gmail.com changed: What|Removed |Added Blocks||12910

[Issue 4733] Possible bugs caused by dynamic arrays in boolean evaluation context

https://issues.dlang.org/show_bug.cgi?id=4733 --- Comment #28 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/D-Programming-Language/druntime https://github.com/D-Programming-Language/druntime/commit/3f50d37b2bed43a82fda3c5fee47b63eaa8765c1 missing

[Issue 12911] New: `std.array.array` doesn't work for non-mutable classes

https://issues.dlang.org/show_bug.cgi?id=12911 Issue ID: 12911 Summary: `std.array.array` doesn't work for non-mutable classes Product: D Version: D2 Hardware: All OS: All Status: NEW Keywords:

[Issue 12894] Make extern(Windows) behave like extern(C) on non-Windows systems

https://issues.dlang.org/show_bug.cgi?id=12894 --- Comment #3 from Sobirari Muhomori dfj1es...@sneakemail.com --- (In reply to Walter Bright from comment #0) I propose changing it to behave like extern(C). This has the advantage that there is significant C code out there that mangles with

[Issue 12900] REG 2.065: Wrong code in IfStatement condition Expression

https://issues.dlang.org/show_bug.cgi?id=12900 --- Comment #7 from Iain Buclaw ibuc...@gdcproject.org --- (In reply to yebblies from comment #3) If it doesn't have a test case or assert in dmd it's probably not going to stay fixed. It's going in the gdc testsuite. :) --

[Issue 12900] REG 2.065: Wrong code in IfStatement condition Expression

https://issues.dlang.org/show_bug.cgi?id=12900 --- Comment #5 from Iain Buclaw ibuc...@gdcproject.org --- https://github.com/D-Programming-Language/dmd/pull/3662 --

[Issue 12900] REG 2.065: Wrong code in IfStatement condition Expression

https://issues.dlang.org/show_bug.cgi?id=12900 --- Comment #6 from Iain Buclaw ibuc...@gdcproject.org --- This is also blocking the next binary release of gdc. --

[Issue 12900] REG 2.065: Wrong code in IfStatement condition Expression

https://issues.dlang.org/show_bug.cgi?id=12900 Iain Buclaw ibuc...@gdcproject.org changed: What|Removed |Added Status|NEW |ASSIGNED

[Issue 12912] New: Lambda function is incorrectly inferred as impure if it uses member field or function

https://issues.dlang.org/show_bug.cgi?id=12912 Issue ID: 12912 Summary: Lambda function is incorrectly inferred as impure if it uses member field or function Product: D Version: D2 Hardware: All OS: All

[Issue 5555] [AA] Built-in associative arrays in pure nothrow functions

https://issues.dlang.org/show_bug.cgi?id= --- Comment #10 from Denis Shelomovskij verylonglogin@gmail.com --- (In reply to bearophile_hugs from comment #9) I suggest to not close this issue until they are also @nogc. https://github.com/D-Programming-Language/druntime/pull/840 --

[Issue 12913] New: Mistake concerning DLists

https://issues.dlang.org/show_bug.cgi?id=12913 Issue ID: 12913 Summary: Mistake concerning DLists Product: D Version: D2 Hardware: x86_64 OS: Windows Status: NEW Severity: trivial Priority: P1

[Issue 12913] Mistake concerning DLists

https://issues.dlang.org/show_bug.cgi?id=12913 safety0ff.bugz safety0ff.b...@gmail.com changed: What|Removed |Added CC|

[Issue 12086] std.algorithm.remove + range of indices produces wrong results

https://issues.dlang.org/show_bug.cgi?id=12086 --- Comment #2 from safety0ff.bugz safety0ff.b...@gmail.com --- (In reply to safety0ff.bugz from comment #1) I think this is a combination of a documentation bug and a remove bug: The documentation bug is that it should accept any range of indices

[Issue 12914] New: std.typecons.alignForSize will not accept immutable names argument

https://issues.dlang.org/show_bug.cgi?id=12914 Issue ID: 12914 Summary: std.typecons.alignForSize will not accept immutable names argument Product: D Version: D2 Hardware: x86_64 OS: Linux Status:

[Issue 11356] isASCII for strings

https://issues.dlang.org/show_bug.cgi?id=11356 --- Comment #2 from monarchdo...@gmail.com --- (In reply to Andrej Mitrovic from comment #1) https://github.com/D-Programming-Language/phobos/pull/1665 I don't know why Walter was so hanged up about this. It's a simple function. I think it's

[Issue 11356] isASCII for strings

https://issues.dlang.org/show_bug.cgi?id=11356 bearophile_h...@eml.cc changed: What|Removed |Added CC||bearophile_h...@eml.cc --- Comment

[Issue 12915] New: RedBlackTree leaks memory

https://issues.dlang.org/show_bug.cgi?id=12915 Issue ID: 12915 Summary: RedBlackTree leaks memory Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal Priority: P1

[Issue 12915] RedBlackTree leaks memory

https://issues.dlang.org/show_bug.cgi?id=12915 --- Comment #1 from Steven Schveighoffer schvei...@yahoo.com --- Can we just null the end node's pointers on the destructor? this should dereference all the nodes. BTW, I think there is a previous bug on that same behavior:

[Issue 12915] RedBlackTree leaks memory

https://issues.dlang.org/show_bug.cgi?id=12915 safety0ff.bugz safety0ff.b...@gmail.com changed: What|Removed |Added CC|

[Issue 12890] std.array index based replace

https://issues.dlang.org/show_bug.cgi?id=12890 safety0ff.bugz safety0ff.b...@gmail.com changed: What|Removed |Added Summary|std.array index based |std.array index

[Issue 12890] std.array index based replace insert

https://issues.dlang.org/show_bug.cgi?id=12890 safety0ff.bugz safety0ff.b...@gmail.com changed: What|Removed |Added Summary|std.array index based |std.array index

[Issue 12916] New: std.array index based insert

https://issues.dlang.org/show_bug.cgi?id=12916 Issue ID: 12916 Summary: std.array index based insert Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P1

[Issue 12915] RedBlackTree leaks memory

https://issues.dlang.org/show_bug.cgi?id=12915 --- Comment #3 from Steven Schveighoffer schvei...@yahoo.com --- OK, I misunderstood. I thought the issue was that the red black tree itself was being pointed at, and that was causing the leak. We certainly can null pointers as the nodes are

[Issue 12915] RedBlackTree leaks memory

https://issues.dlang.org/show_bug.cgi?id=12915 --- Comment #4 from safety0ff.bugz safety0ff.b...@gmail.com --- (In reply to Steven Schveighoffer from comment #3) We certainly can null pointers as the nodes are deallocated. But the tree does not go through and destroy all the nodes if you just

[Issue 8280] std.array.uninitializedArrayExtend, std.array.initializedArray

https://issues.dlang.org/show_bug.cgi?id=8280 bearophile_h...@eml.cc changed: What|Removed |Added Summary|std.array.uninitializedArra |std.array.uninitializedArra

[Issue 8280] std.array.uninitializedArrayExtend, std.array.initializedArray

https://issues.dlang.org/show_bug.cgi?id=8280 safety0ff.bugz safety0ff.b...@gmail.com changed: What|Removed |Added CC|

[Issue 10930] std.array.replace cannot simple replace an element in array

https://issues.dlang.org/show_bug.cgi?id=10930 safety0ff.bugz safety0ff.b...@gmail.com changed: What|Removed |Added CC|

[Issue 10930] std.array.replace cannot simple replace an element in array

https://issues.dlang.org/show_bug.cgi?id=10930 --- Comment #2 from safety0ff.bugz safety0ff.b...@gmail.com --- Also, replaceInPlace and replaceSlice are better candidates for this type of operation. --

[Issue 8280] std.array.uninitializedArrayExtend, std.array.initializedArray

https://issues.dlang.org/show_bug.cgi?id=8280 --- Comment #3 from bearophile_h...@eml.cc --- (In reply to bearophile_hugs from comment #1) auto data = initializedArray!(char[])(100, ' '); It is equivalent to: auto data = uninitializedArray!(char[])(100); data[] = ' '; Another

[Issue 8280] std.array.uninitializedArrayExtend, std.array.initializedArray

https://issues.dlang.org/show_bug.cgi?id=8280 --- Comment #4 from bearophile_h...@eml.cc --- (In reply to bearophile_hugs from comment #3) auto funcs = initializedArray!(int function(int)[])(10, i = i); There can be some very uncommon strange cases, but that's a value and not a lambda to fill