On 16/04/2023 1:20 AM, kdevel wrote:
On Saturday, 15 April 2023 at 12:45:31 UTC, Richard (Rikki) Andrew Cattermole wrote:
It was bad analysis by the compiler, which has since been corrected.

It should have been applied only to @safe code.

But why is the @unsafe programmer now left unprotected in cases like this

```
ref int foo (ref int i)
//           `------- automatically insert `return` here?
{
    return i;
}
```

where the compiler recognizes that the function returns a ref parameter?

Under which circumstances is it a mistake to insert the `return` at the indicated position? If there are none why can't it be done implicitly (automatically)?

@system (which is currently the default, there is a strong desire to change this), does no safety checks.

You are on your own to do whatever unsafe thing you want.

If you want safety checks, use @safe.
  • Re: Returning a ... IchorDev via Digitalmars-d-learn
  • Re: Returning a ... Paul Backus via Digitalmars-d-learn
  • Re: Returning a ... Jacob Shtokolov via Digitalmars-d-learn
    • Re: Returni... kdevel via Digitalmars-d-learn
      • Re: Ret... Bastiaan Veelo via Digitalmars-d-learn
        • Re:... kdevel via Digitalmars-d-learn
          • ... Dennis via Digitalmars-d-learn
            • ... kdevel via Digitalmars-d-learn
              • ... Richard (Rikki) Andrew Cattermole via Digitalmars-d-learn
              • ... kdevel via Digitalmars-d-learn
              • ... Richard (Rikki) Andrew Cattermole via Digitalmars-d-learn
              • ... kdevel via Digitalmars-d-learn
              • ... Dennis via Digitalmars-d-learn
              • ... Dennis via Digitalmars-d-learn
              • ... kdevel via Digitalmars-d-learn
              • ... Dennis via Digitalmars-d-learn
              • ... kdevel via Digitalmars-d-learn
              • ... Dennis via Digitalmars-d-learn

Reply via email to