September 09 General » Re: Discussion about deprecating @nogc and workarounds | |||
|---|---|---|---|
| |||
...call the GC, and cannot be the "owner" of the GC allocations it uses). 7... | |||
September 05 DIP Ideas » Re: Escape Analysis & Owner Escape Analysis | |||
|---|---|---|---|
| |||
...ptr;
}
void caller() {
scope Thing owner;
called(owner); // Error: owner would escape to an unknown... | |||
September 05 DIP Ideas » Re: Escape Analysis & Owner Escape Analysis | |||
|---|---|---|---|
| |||
Wait, so how would one force owner escape analysis to be enabled for manually heap... | |||
September 04 DIP Ideas » Re: Escape Analysis & Owner Escape Analysis | |||
|---|---|---|---|
| |||
Walter has stated that in the past, but it shouldn't necessarily mean we should... | |||
September 05 DIP Ideas » Re: Escape Analysis & Owner Escape Analysis | |||
|---|---|---|---|
| |||
In theory yes it's perfectly safe. However this example isn't meant to show... | |||
September 04 DIP Ideas » Re: Escape Analysis & Owner Escape Analysis | |||
|---|---|---|---|
| |||
But aren’t segfault always meant to be @safe anyway? ```d int* x; void main() @safe... | |||
September 04 DIP Ideas » Re: Escape Analysis & Owner Escape Analysis | |||
|---|---|---|---|
| |||
...void func(ref Top owner) @safe {
int** field = &owner.field;
// owner is now effectively const... | |||
September 04 DIP Ideas » Re: Escape Analysis & Owner Escape Analysis | |||
|---|---|---|---|
| |||
...void func(ref Top owner) @safe {
int* field = owner.field;
// owner is now effectively const... | |||
September 04 DIP Ideas » Re: Escape Analysis & Owner Escape Analysis | |||
|---|---|---|---|
| |||
...here, owner escape analysis only kicks in and forces effectively const on the owner if... | |||
September 03 DIP Ideas » Re: Escape Analysis & Owner Escape Analysis | |||
|---|---|---|---|
| |||
The description is getting clearer every revision, props for that. But it's also becoming... | |||
Copyright © 1999-2021 by the D Language Foundation