[Issue 19747] No debug line info for code in scope(exit)

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19747 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 19605] invalid forward reference error when getting the `.sizeof` of an opaque enum

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19605 Basile-z changed: What|Removed |Added Keywords|pull, rejects-valid | --

[Issue 19605] invalid forward reference error when getting the `.sizeof` of an opaque enum

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19605 --- Comment #3 from Basile-z --- This one might be invalid actually. The implementation of the fix is problematic at least. --

[Issue 19605] invalid forward reference error when getting the `.sizeof` of an opaque enum

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19605 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #2 from Dlang Bot ---

[Issue 19605] invalid forward reference error when getting the `.sizeof` of an opaque enum

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19605 Basile-z changed: What|Removed |Added Summary|invalid forward reference |invalid forward reference

[Issue 19605] invalid forward reference error when getting the `.sizeof` if an opaque enum

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19605 Basile-z changed: What|Removed |Added Keywords||rejects-valid CC|

[Issue 19747] No debug line info for code in scope(exit)

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19747 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #1 from Dlang Bot ---

[Issue 5725] ubyte/ushort infinite foreach loops

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5725 Basile-z changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 19748] New: [REG][wrong codegen] Returning 4 floats + DMD + 64-bit

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19748 Issue ID: 19748 Summary: [REG][wrong codegen] Returning 4 floats + DMD + 64-bit Product: D Version: D2 Hardware: x86_64 OS: Windows Status: NEW Severity:

[Issue 19747] New: No debug line info for code in scope(exit)

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19747 Issue ID: 19747 Summary: No debug line info for code in scope(exit) Product: D Version: D2 Hardware: x86_64 OS: Windows Status: NEW Keywords: symdeb

[Issue 19621] The specification is self-contradictory on immutability

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19621 ZombineDev changed: What|Removed |Added CC||petar.p.ki...@gmail.com --

[Issue 19602] Under some circumstances: throwing Error subclasses unwinds without invoking dtors

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19602 --- Comment #13 from Jacob Carlborg --- (In reply to Walter Bright from comment #11) > Unittest failures at the top level do not call the assert fail handler, they > call _d_unittestp(), which then calls the assert error handler. This means > you

[Issue 19602] Under some circumstances: throwing Error subclasses unwinds without invoking dtors

2019-03-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19602 --- Comment #12 from Eyal --- Walter, the question is: what benefits does the current approach have over a much safer approach of having *only* "onError" callbacks that allow the user to write some handling code in case of error before abort? 1)