Escape Analysis & Owner Escape Analysis

[Richard (Rikki) Andrew Cattermole]

On 22/09/2024 11:03 PM, IchorDev wrote:
>                   * |@escape| is the opposite of |@escape()|, which
>                     could be confusing
> 
>             Originally I was going to make this to mean 'inferred', but
>             it's better if everything gets inferred by default.
> 
>             It needs to mean something, so got an alternative?
> 
>         Maybe add a special case for something like |@escape(false)|?
> 
>     The question is for what |@escape()| would do. Which Dennis has not
>     counter proposal for.
> 
> I see. |@escape| is meant to tell you how the variable escapes, but on 
> its own it implicitly uses a default set of escapes. If the parentheses 
> are empty, surely that should just be the same as |@escape|?

No, ``@escape()`` specifies the empty set. As in, it does not escape 
anywhere.

With ``@escape`` no set has been given.

I'm wondering if it shouldn't be specified but instead let buildkite 
determine what ``@escape`` does based upon statistics.