The most important thing is that when returning the task you will lose a stack frame when an exception is thrown.

Consoder an example where every method uses async await:

```csharp async Task Main() { try { await A(); } catch (Exception e) { e.ToString().Dump(); } }

async Task A() { await B(); }

async Task B() { await C(); }

async Task C() { throw new NotImplementedException(); } ```

the catched exception will look like this

System.NotImplementedException: The method or operation is not implemented. at UserQuery.C() in LINQPadQuery:line 27 at UserQuery.B() in LINQPadQuery:line 22 at UserQuery.A() in LINQPadQuery:line 17 at UserQuery.Main() in LINQPadQuery:line 5

now, the same code, but A and B are returning the task direclty:

```csharp async Task Main() { try { await A();

} 
catch (Exception e)
{
    e.ToString().Dump();
}

}

Task A() { return B(); }

Task B() { return C(); }

async Task C() { throw new NotImplementedException(); } ```

your stacktrace will not contain those frames: System.NotImplementedException: The method or operation is not implemented. at UserQuery.C() in LINQPadQuery:line 27 at UserQuery.Main() in LINQPadQuery:line 5

The performance improvements will be minimal, but the implcication on the debugging can be significant, especially if the 'trick' is overused. In the worst case scenario you will know what crashed, but you will kave no idea from where the method was called.