le to
call the print(), though, and it just prints garbage. Should this be a compiler
error?
wtf.p.print() is called, x has gone out of scope. It's still possible to
> call the print(), though, and it just prints garbage. Should this be a
> compiler error?
Either way, you should submit a bugzilla entry.
Why should he file a bug report for something that's not a bug?
Mike L. Wrote:
> The following code compiles fine for me with dmd 1.043:
[snip]
> Should this be a compiler error?
No, because what you are asking for requires full escape analysis (that is,
determining if a variable escapes its scope). In order to do that, dmd needs
full sources
