[Issue 24520] [REG] type(value) got a synonym (type)(value)

https://issues.dlang.org/show_bug.cgi?id=24520 Nick Treleaven changed: What|Removed |Added CC||n...@geany.org Severity|regressio

[Issue 24454] Disallow initialization of non-static reference type data members by non-immutable values or rvalues

https://issues.dlang.org/show_bug.cgi?id=24454 --- Comment #4 from Bolpat --- (In reply to Steven Schveighoffer from comment #1) > case c2 seems fine to me. What is the problem with it? This seems akin to > string interning. Strings barely have identity, but class objects in general have identit

[Issue 23964] [REG2.102] inccorect error opAssign cannot be used ... @disable

https://issues.dlang.org/show_bug.cgi?id=23964 --- Comment #3 from johanenge...@weka.io --- > A workaround is to make `foo` @safe. That will make the code to compile. Thanks, this indeed works and helps me out again now. A big problem with this bug is that it is _very_ hard to find the reason for

[Issue 24528] Add offending member to "no size because of forward reference" error

https://issues.dlang.org/show_bug.cgi?id=24528 basile-z changed: What|Removed |Added Keywords||diagnostic --

[Issue 24496] "Undefined reference to internal" when -c with SysTime.max in init

https://issues.dlang.org/show_bug.cgi?id=24496 kinke changed: What|Removed |Added Keywords||backend --

[Issue 24496] "Undefined reference to internal" when -c with SysTime.max in init

https://issues.dlang.org/show_bug.cgi?id=24496 kinke changed: What|Removed |Added CC||ki...@gmx.net --- Comment #2 from kinke --- Oh nice

[Issue 24525] auto ref lambda exp not parsed if used as left-most expression in an expression statement

https://issues.dlang.org/show_bug.cgi?id=24525 basile-z changed: What|Removed |Added Summary|auto ref lambda exp not |auto ref lambda exp not |parsed

[Issue 24525] auto ref lambda exp not parsed if used as left-most expression in a expression statement

https://issues.dlang.org/show_bug.cgi?id=24525 --- Comment #3 from basile-z --- > Any ambiguities in the grammar between Statements and Declarations are > resolved by the declarations taking precedence. yes, I remember the spec about decl/stmt ambiguities but here I think there are none. The

[Issue 24481] retro no longer works with types that support assignment but not moving

https://issues.dlang.org/show_bug.cgi?id=24481 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 24528] Add offending member to "no size because of forward reference" error

https://issues.dlang.org/show_bug.cgi?id=24528 johanenge...@weka.io changed: What|Removed |Added Keywords||industry --

[Issue 24528] New: Add offending member to "no size because of forward reference" error

https://issues.dlang.org/show_bug.cgi?id=24528 Issue ID: 24528 Summary: Add offending member to "no size because of forward reference" error Product: D Version: D2 Hardware: All OS: All Status: NEW