@trusted assumptions about @safe code

Walter Bright newshound2 at digitalmars.com
Wed May 27 10:07:58 UTC 2020


On 5/26/2020 10:23 AM, Timon Gehr wrote:
> On 26.05.20 15:19, ag0aep6g wrote:
>> On 26.05.20 11:35, Walter Bright wrote:
>>> On 5/26/2020 12:07 AM, Timon Gehr wrote:
>>>> I don't think so. @trusted code can't rely on @safe code behaving a certain 
>>>> way to ensure memory safety, it has to be defensive.
>>>
>>> I agree. The trusted code here is not passing safe arguments to g(), but it 
>>> is trusted to do so.
>>
>> Nice. Timon and Walter agree on something related to safety.
> 
> (We agree on many things. It just does not seem that way because I seldomly get 
> involved when I agree with a decision.)

It is indeed nice when we agree. I appreciate it.


More information about the Digitalmars-d mailing list