[Issue 17318] Delegates allow escaping reference to stack variable

2018-03-10 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17318 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 17318] Delegates allow escaping reference to stack variable

2018-03-03 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17318 Walter Bright changed: What|Removed |Added Keywords||safe

[Issue 17318] Delegates allow escaping reference to stack variable

2018-01-20 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17318 --- Comment #3 from hst...@quickfur.ath.cx --- P.S. On my computer, the value of z changes after the call to dg(), which is wrong because z is a local variable in smoke() that the delegate should not be able to access. --

[Issue 17318] Delegates allow escaping reference to stack variable

2018-01-20 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17318 --- Comment #2 from hst...@quickfur.ath.cx --- It could be because the compiler now is smarter about constructing return values in-place rather than moving the struct afterwards. Nevertheless, the actual problem still persists: the delegate is

[Issue 17318] Delegates allow escaping reference to stack variable

2018-01-20 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17318 Carsten Blüggel changed: What|Removed |Added CC||chi...@posteo.net ---

[Issue 17318] Delegates allow escaping reference to stack variable

2017-04-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17318 hst...@quickfur.ath.cx changed: What|Removed |Added Keywords||accepts-invalid --