Encapsulating trust

[David Nadlinger via Digitalmars-d]

On Tuesday, 2 September 2014 at 18:50:19 UTC, Walter Bright wrote:
> On 9/2/2014 10:20 AM, Daniel Murphy wrote:
>> Having syntax (or a wrapper function) to do the second 
>> wrapping automatically
>> would violate @safe.  If it was syntax, it would be banned in 
>> @safe.  If it's a
>> wrapping method like the proposed 'call', then it is a program 
>> error for it to
>> be marked @trusted.
>
> I agree with monarch_data, this is the executive summary, the 
> salient point, the money shot, etc.

+1 from me as the self-proclaimed resident @safe-ty philosopher. 
We might want to think about fixing the immediately invoked 
delegate literal inlining problem.

David