[ 
https://issues.apache.org/jira/browse/BEAM-14347?focusedWorklogId=761794&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-761794
 ]

ASF GitHub Bot logged work on BEAM-14347:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Apr/22 13:36
            Start Date: 25/Apr/22 13:36
    Worklog Time Spent: 10m 
      Work Description: damccorm commented on PR #17429:
URL: https://github.com/apache/beam/pull/17429#issuecomment-1108585124

   > but how do you feel about merging this after the 2.39 cut, so the first 
release that requires Go 1.18 is 2.40?
   
   That's fine by me - is your goal just to get some additional validation with 
all of us building stuff on Go 1.18 for a while?
   
   > Whenever we merge it though, this PR must also include a note in 
CHANGES.md for whichever version it affects
   
   Yeah, I was planning on adding something in CHANGES.md in a follow up pr 
(along with doc changes) once all the generics work is in - I can also add a 
placeholder in this PR once 2.39 is cut (and the 2.40 release notes are ready) 
though




Issue Time Tracking
-------------------

    Worklog Id:     (was: 761794)
    Time Spent: 1.5h  (was: 1h 20m)

> [Go SDK] Allow users to optimize DoFns with a single generic registration 
> function
> ----------------------------------------------------------------------------------
>
>                 Key: BEAM-14347
>                 URL: https://issues.apache.org/jira/browse/BEAM-14347
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-go
>            Reporter: Danny McCormick
>            Assignee: Danny McCormick
>            Priority: P2
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Right now, to optimize DoFn execution, users have to use the code generator. 
> This updates to allow them to use generics instead.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to