On Monday, 13 June 2016 at 14:16:58 UTC, jmh530 wrote:
So returning a reference to something on the stack is a bad
idea, but copying the value would be fine.
This is easy enough to get wrong elsewhere too. I recall having
an issue with a foreach, until I added a 'ref' to it. Looking at
the a
On Monday, 13 June 2016 at 01:41:07 UTC, Mike Parker wrote:
Everything works fine in your example because 'new' always
allocates on the heap. Anything allocated on the stack is not
guaranteed to be valid after the scope exits:
struct Foo
{
int baz;
~this() { baz = 1; }
}
void main()
On Sunday, 12 June 2016 at 18:24:58 UTC, jmh530 wrote:
garbage collected variable and assign it to it. Everything
seems to work fine. I'm just not sure if there are any gotchas
to be aware of.
class Foo
{
int baz = 2;
}
void main()
{
import std.stdio : writeln;
On Sunday, 12 June 2016 at 19:30:49 UTC, Era Scarecrow wrote:
On Sunday, 12 June 2016 at 18:24:58 UTC, jmh530 wrote:
I'm just not sure if there are any gotchas to be aware of.
Aside from forgetting it's it's own block, you might add a
return statement to it and leave the entire function. Or
On Sunday, 12 June 2016 at 18:24:58 UTC, jmh530 wrote:
I'm just not sure if there are any gotchas to be aware of.
Aside from forgetting it's it's own block, you might add a
return statement to it and leave the entire function. Or forget
what's in what scope (assuming you do more than 1-2 pag
