TaskResultExecutor is never used by ActionMethodExecutor

[pentp]

Describe the bug

Due to the order of executors in ActionMethodExecutor.Executors, a Task returning action is always executed through AwaitableResultExecutor instead of TaskResultExecutor. From the ordering of the types and comments it looks like this wasn't the original intention and is sub-optimal (and the type is essentially unused currently).

Expected Behavior

Task returning actions are executed using TaskResultExecutor.

Thanks for contacting us.
We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.