February 07, 2013 Re: make @safe "non-escapable"? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Johannes Pfau | Am Thu, 7 Feb 2013 08:46:55 +0100
schrieb Johannes Pfau <nospam@example.com>:
> Am Wed, 06 Feb 2013 22:46:50 +0400
> schrieb Dmitry Olshansky <dmitry.olsh@gmail.com>:
>
> > 06-Feb-2013 22:26, Robert пишет:
> > > Guaranteeing that the code in app.cfg has to be safe.
> > >
> > > I thought of some wrapper like safeImport() which searches the code for @system or @trusted and rejects the code if one of them is found. But this is quite hard to do it right, especially with mixin's. So it's probably best if the compiler handles this.
> > >
> > > What do you think. Should I file a bug report?
> > >
> >
> > Yup.
> >
>
> But isn't @system completely useless if it can't overwrite @safe as @system is always the default?
>
Seems this was already discussed on the bug tracker, I should have read the bug report first :-)
|
February 07, 2013 Re: make @safe "non-escapable"? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Johannes Pfau | On Thursday, 7 February 2013 at 07:47:00 UTC, Johannes Pfau wrote:
> But isn't @system completely useless if it can't overwrite @safe as @system is always the default?
@safe:
//not in struct/larger declaration so is acceptable
@system {
void func();
}
|
Copyright © 1999-2021 by the D Language Foundation