[ARROW-4717] [C#] Consider exposing ValueTask instead of Task

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.14.0
• Component/s: C#
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/21241
• Assignee: Eric Erhardt
• Reporter: Eric Erhardt
• Created: 28/Feb/19 18:29
• Updated: 11/Jan/23 07:35
• Resolved: 30/Apr/19 14:37

Description

See https://github.com/apache/arrow/pull/3736#pullrequestreview-207169204 for the discussion and https://devblogs.microsoft.com/dotnet/understanding-the-whys-whats-and-whens-of-valuetask/ for the reasoning.

Using `Task<T>` in public API requires that a new Task instance be allocated on every call. When returning synchronously, using ValueTask will allow the method to not allocate.

In order to do this, we will need to take a new dependency on  System.Threading.Tasks.Extensions NuGet package.

Issue Links

• links to: GitHub Pull Request #4194