[ https://issues.apache.org/jira/browse/ARROW-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17661739#comment-17661739 ]
Rok Mihevc commented on ARROW-4717: ----------------------------------- This issue has been migrated to [issue #21241|https://github.com/apache/arrow/issues/21241] on GitHub. Please see the [migration documentation|https://github.com/apache/arrow/issues/14542] for further details. > [C#] Consider exposing ValueTask instead of Task > ------------------------------------------------ > > Key: ARROW-4717 > URL: https://issues.apache.org/jira/browse/ARROW-4717 > Project: Apache Arrow > Issue Type: Improvement > Components: C# > Reporter: Eric Erhardt > Assignee: Eric Erhardt > Priority: Major > Labels: pull-request-available > Fix For: 0.14.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)