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

Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/07/12 14:05:03 UTC

[jira] [Assigned] (ARROW-12177) [C++] Investigate moving away from std::function in AsyncGenerator

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

Todd Farmer reassigned ARROW-12177:
-----------------------------------

    Assignee:     (was: Weston Pace)

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [C++] Investigate moving away from std::function in AsyncGenerator
> ------------------------------------------------------------------
>
>                 Key: ARROW-12177
>                 URL: https://issues.apache.org/jira/browse/ARROW-12177
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Weston Pace
>            Priority: Major
>              Labels: async-util
>
> Most of async_generator.h uses std::function to store the operator functions.  Primarily this was to simplify the implementation.  However, now that it is being used more it ends up being somewhat wordy because lambda cannot be implicitly assigned to std::function.  This has gotten to the point where we have created templated overloads that wrap the lambdas in functions.
> It may be time to take a second look at this decision and converting over to templated callable types.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)