[Issue 24358] New: std.digest on array of arrays surprisingly shallow

https://issues.dlang.org/show_bug.cgi?id=24358 Issue ID: 24358 Summary: std.digest on array of arrays surprisingly shallow Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement

[Issue 24349] object noreturn link is missing

https://issues.dlang.org/show_bug.cgi?id=24349 --- Comment #3 from Jim Balter --- I guess I should have been more explicit. It isn't just that the link is missing ... this is also wrong: alias noreturn = Nn; I doubt that the fix for the link fixed this ... is there some way to look at the

[Issue 24345] Issue with `alias this = xyz` inside structs.

https://issues.dlang.org/show_bug.cgi?id=24345 timon.g...@gmx.ch changed: What|Removed |Added CC||timon.g...@gmx.ch --- Comment #1 from

[Issue 23868] Compiler-generated opAssign has very high stack frame usage

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

[Issue 23414] Import order emits "Error: no size because of forward references"

https://issues.dlang.org/show_bug.cgi?id=23414 --- Comment #5 from Richard Cattermole --- My assumption has been that this isn't fixable, but worth documenting. Each module has one public declaration a struct. Which in turn uses similar structs in other modules. ASCII, UTF-8, UTF-16, UTF-32

[Issue 23414] Import order emits "Error: no size because of forward references"

https://issues.dlang.org/show_bug.cgi?id=23414 --- Comment #4 from Walter Bright --- I would like to fix this, once a smallish test case can be devised. But keep in mind some things cannot be fixed. At least the compiler issues an error for those cases. An example: struct S { static if

[Issue 11080] assert(`string`) should be forbidden

https://issues.dlang.org/show_bug.cgi?id=11080 Nick Treleaven changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Issue 14387] Disallow string literals as assert conditions

https://issues.dlang.org/show_bug.cgi?id=14387 Nick Treleaven changed: What|Removed |Added CC||temta...@gmail.com --- Comment #7 from

[Issue 18788] static arrays with a length specified at runtime should dynamically allocate on the stack

https://issues.dlang.org/show_bug.cgi?id=18788 Nick Treleaven changed: What|Removed |Added CC||n...@geany.org --- Comment #9 from Nick

[Issue 24357] String spec needs updating

https://issues.dlang.org/show_bug.cgi?id=24357 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #1 from Dlang Bot --- @ntrel

[Issue 24357] New: String spec needs updating

https://issues.dlang.org/show_bug.cgi?id=24357 Issue ID: 24357 Summary: String spec needs updating Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: normal Priority: P1

[Issue 24355] Slice copy with static arrays incorrect bounds checking

https://issues.dlang.org/show_bug.cgi?id=24355 --- Comment #5 from Nick Treleaven --- Spec for above: > A string literal converts to a static array rvalue of the same or longer > length https://dlang.org/spec/expression.html#string_literals --

[Issue 24355] Slice copy with static arrays incorrect bounds checking

https://issues.dlang.org/show_bug.cgi?id=24355 --- Comment #4 from Nick Treleaven --- > An array *initializer* is allowed to have fewer elements. Actually that only seems to apply when the initializer is a string literal. char[4] s = [1]; // error char[4] s = "a"; // OK --

[Issue 24355] Slice copy with static arrays incorrect bounds checking

https://issues.dlang.org/show_bug.cgi?id=24355 Nick Treleaven changed: What|Removed |Added CC||n...@geany.org --- Comment #3 from Nick