https://issues.dlang.org/show_bug.cgi?id=9352
RazvanN changed:
What|Removed |Added
CC||luka8...@owave.net
--- Comment #5 from RazvanN
https://issues.dlang.org/show_bug.cgi?id=9352
hst...@quickfur.ath.cx changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
http://d.puremagic.com/issues/show_bug.cgi?id=9352
Adam D. Ruppe destructiona...@gmail.com changed:
What|Removed |Added
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=9352
--- Comment #2 from hst...@quickfur.ath.cx 2013-01-18 12:22:26 PST ---
You're right, I added some writeln's to print the address of S.t, and here's
what I got:
ctor: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20,
http://d.puremagic.com/issues/show_bug.cgi?id=9352
--- Comment #3 from hst...@quickfur.ath.cx 2013-01-18 12:25:33 PST ---
Rather than banning this outright, I think a better approach may be to detect
when a delegate is referencing the struct on the stack, and create the struct
on the heap
