@trusted attribute should be replaced with @trusted blocks
Joseph Rushton Wakeling
joseph.wakeling at webdrake.net
Wed Jan 15 18:41:06 UTC 2020
On Wednesday, 15 January 2020 at 18:06:11 UTC, ag0aep6g wrote:
> I don't think that's what Steven had in mind. In that world,
> @safe would be very, very limited, because it couldn't be
> allowed to call @trusted functions.
Well, apologies to Steven if I've misinterpreted his proposal.
But what I had in mind was that @safe would be able to call
@trusted just as it does now.
So, put that together with what I wrote above, and you have
something that allows better validation of the internals of
@trusted functions, and still gives the user clarity about which
functions are safe in their own terms, and which are safe based
on some programmer provided guarantees.
More information about the Digitalmars-d
mailing list