[Issue 17606] dmd wrongly accepts field without type when annotated with a UDA

https://issues.dlang.org/show_bug.cgi?id=17606 Vladimir Panteleev changed: What|Removed |Added Hardware|x86 |All

[Issue 15304] [REG 2.068.0] Error about SortedRange not being nothrow in debug mode

https://issues.dlang.org/show_bug.cgi?id=15304 --- Comment #6 from Vladimir Panteleev --- Fixed by https://github.com/dlang/dmd/pull/5881. --

[Issue 17601] [REG2.075.0-b1] segmentation fault for dmd -deps

https://issues.dlang.org/show_bug.cgi?id=17601 --- Comment #2 from Vladimir Panteleev --- Reduced: a.d import b; b.d void foo() { import c; } c.d struct { void () }

[Issue 17605] [REG2.066.0] __traits(compiles, closure) adds link-time reference to _d_allocmemory

https://issues.dlang.org/show_bug.cgi?id=17605 Vladimir Panteleev changed: What|Removed |Added Summary|__traits(compiles, closure)

[Issue 17614] [REG2.075.0-b2] __VERSION__ has the wrong value

https://issues.dlang.org/show_bug.cgi?id=17614 greenify changed: What|Removed |Added CC||greensunn...@gmail.com ---

[Issue 17608] [REG2.075.0-b2] No [] operator overload for type object.TypeInfo_Class

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

[Issue 17614] New: [REG2.075.0-b2] __VERSION__ has the wrong value

https://issues.dlang.org/show_bug.cgi?id=17614 Issue ID: 17614 Summary: [REG2.075.0-b2] __VERSION__ has the wrong value Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: regression

[Issue 17612] [REG2.063] Segmentation fault with bad object.d

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

[Issue 16564] KRRegion.empty sometimes returns Ternary.no

https://issues.dlang.org/show_bug.cgi?id=16564 --- Comment #5 from Vladimir Panteleev --- (In reply to Temtaime from comment #4) > ubyte[1024 * 1024] buf; Are you sure that's not just because you have a 1MB static array on the stack? This program, by

[Issue 17369] [Module std.traits] Documentation lists ditto in table

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

[Issue 17369] [Module std.traits] Documentation lists ditto in table

https://issues.dlang.org/show_bug.cgi?id=17369 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/43eadc38e3e31258470b53237db4176876ad54c5 Fix Issue 17369 - [Module std.traits] Documentation

[Issue 8472] Replace walkLength() with an improved count()

https://issues.dlang.org/show_bug.cgi?id=8472 --- Comment #2 from Andrei Alexandrescu --- thx! --

[Issue 8472] Replace walkLength() with an improved count()

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

[Issue 4923] immutable module variables are modifiable in non-shared module constructors

https://issues.dlang.org/show_bug.cgi?id=4923 Steven Schveighoffer changed: What|Removed |Added Keywords|pull|

[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

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

[Issue 4923] immutable module variables are modifiable in non-shared module constructors

https://issues.dlang.org/show_bug.cgi?id=4923 --- Comment #7 from Steven Schveighoffer --- *** Issue 6114 has been marked as a duplicate of this issue. *** --

[Issue 17540] std.net.curl: HTTP no possibillity to set CURLOPT_NOPROXY

https://issues.dlang.org/show_bug.cgi?id=17540 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/e40a35675a89ec9346ba90cf973a423ff8e5d973 Fix Issue 17540 - std.net.curl: HTTP no possibillity to

[Issue 17613] New: Inconsistent behaviour in code coverage

https://issues.dlang.org/show_bug.cgi?id=17613 Issue ID: 17613 Summary: Inconsistent behaviour in code coverage Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: normal

[Issue 17608] [REG2.075.0-b2] No [] operator overload for type object.TypeInfo_Class

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

[Issue 17601] [REG2.075.0-b1] segmentation fault for dmd -deps

https://issues.dlang.org/show_bug.cgi?id=17601 --- Comment #1 from Vladimir Panteleev --- Reducing. --

[Issue 17605] __traits(compiles, closure) adds link-time reference to _d_allocmemory

https://issues.dlang.org/show_bug.cgi?id=17605 --- Comment #2 from ZombineDev --- Agreed. From my superficial understanding of dmd's internals, I think the culprit is around `needsCodegen()`. AFAIR, changes to that code often led to regressions and undefined symbol

[Issue 17605] __traits(compiles, closure) adds link-time reference to _d_allocmemory

https://issues.dlang.org/show_bug.cgi?id=17605 Adam D. Ruppe changed: What|Removed |Added CC|

[Issue 17602] improve message for deprecated enum comparison

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

[Issue 17612] [REG2.063] Segmentation fault with bad object.d

https://issues.dlang.org/show_bug.cgi?id=17612 Vladimir Panteleev changed: What|Removed |Added Priority|P1 |P5

[Issue 17612] New: [REG2.063] Segmentation fault with bad object.d

https://issues.dlang.org/show_bug.cgi?id=17612 Issue ID: 17612 Summary: [REG2.063] Segmentation fault with bad object.d Product: D Version: D2 Hardware: All OS: All Status: NEW Keywords: ice

[Issue 15625] Internal error: backend/elfobj.c 1014

https://issues.dlang.org/show_bug.cgi?id=15625 Marco Leise changed: What|Removed |Added CC||marco.le...@gmx.de ---

[Issue 17599] Abbreviate too long type definitions in error messages

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

[Issue 4851] Three suggestions for std.random

https://issues.dlang.org/show_bug.cgi?id=4851 RazvanN changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Issue 17440] Nullable.nullify() resets referenced object

https://issues.dlang.org/show_bug.cgi?id=17440 --- Comment #6 from RazvanN --- (In reply to Marenz from comment #5) > Closing? Well.. It is _very_ unexpected that Nullable would just follow a > reference and kills everything. It's like you add a pointer to an array and

[Issue 17596] dmd d 2.073.2 and 2.074.1 interim generated dmd segfaults on FreeBSD 12-CURRENT

https://issues.dlang.org/show_bug.cgi?id=17596 --- Comment #4 from Vladimir Panteleev --- (In reply to Cy Schubert from comment #3) > The implementer of inode64 has done a great job of avoiding ABI breakage. > Applications built before inode64 continue to run

[Issue 17440] Nullable.nullify() resets referenced object

https://issues.dlang.org/show_bug.cgi?id=17440 --- Comment #5 from Marenz --- Closing? Well.. It is _very_ unexpected that Nullable would just follow a reference and kills everything. It's like you add a pointer to an array and after setting it to null your pointed

[Issue 17440] Nullable.nullify() resets referenced object

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

[Issue 17440] Nullable.nullify() resets referenced object

https://issues.dlang.org/show_bug.cgi?id=17440 --- Comment #4 from RazvanN --- Eveyone ok with closing this? --

[Issue 17600] implicit float->int cast using += operator

https://issues.dlang.org/show_bug.cgi?id=17600 --- Comment #2 from Simon --- I expected "x += y" to be equivalent to "x = x + y" (in which case an error is generated). Sorry I didn't check the spec, everything is actually correct. (but really surprising behavior

[Issue 17440] Nullable.nullify() resets referenced object

https://issues.dlang.org/show_bug.cgi?id=17440 --- Comment #3 from Marenz --- >Is there any particular reason you need to use Nullify with a class type >instead of simply using the class type directly and use "null" to indicate the >unset state? There is no

[Issue 17440] Nullable.nullify() resets referenced object

https://issues.dlang.org/show_bug.cgi?id=17440 --- Comment #2 from Vladimir Panteleev --- (In reply to Marenz from comment #0) > I am not sure if it is desired, but it was highly unintuitive and unexpected > for me: > > If you use Nullable with a class type

[Issue 17227] deprecation messages building Phobos

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

[Issue 11594] synchronized causing segfault instead of Error.

https://issues.dlang.org/show_bug.cgi?id=11594 --- Comment #3 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/a2ead6dd04efdfeb283b72daf167e85fe8db9c49 Fix issue 11594: Check if the monitor is null in

[Issue 11594] synchronized causing segfault instead of Error.

https://issues.dlang.org/show_bug.cgi?id=11594 github-bugzi...@puremagic.com changed: What|Removed |Added Resolution|WORKSFORME |FIXED --

[Issue 17369] [Module std.traits] Documentation lists ditto in table

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

[Issue 17611] New: core.demangle cannot demangle delegates with function attributes

https://issues.dlang.org/show_bug.cgi?id=17611 Issue ID: 17611 Summary: core.demangle cannot demangle delegates with function attributes Product: D Version: D2 Hardware: x86_64 OS: Windows Status: