You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Eric Erhardt (JIRA)" <ji...@apache.org> on 2019/04/24 19:38:00 UTC

[jira] [Assigned] (ARROW-4717) [C#] Consider exposing ValueTask instead of Task

     [ https://issues.apache.org/jira/browse/ARROW-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Erhardt reassigned ARROW-4717:
-----------------------------------

    Assignee: Eric Erhardt

> [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
>          Time Spent: 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
(v7.6.3#76005)