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

Posted to issues@beam.apache.org by "Robert Burke (Jira)" <ji...@apache.org> on 2022/01/13 18:37:00 UTC

[jira] [Updated] (BEAM-6578) Consider allowing value types to use pointer coders

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

Robert Burke updated BEAM-6578:
-------------------------------
    Resolution: Abandoned
        Status: Resolved  (was: Open)

> Consider allowing value types to use pointer coders
> ---------------------------------------------------
>
>                 Key: BEAM-6578
>                 URL: https://issues.apache.org/jira/browse/BEAM-6578
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>    Affects Versions: Not applicable
>            Reporter: Robert Burke
>            Priority: P3
>
> With the coder registry, there are certain addition bits of complexity to permit or deny. 
> In particular: Should Value types be automatically promoted by beam to use the pointer version of a coder, should one exist?
> Offhand: My inclination is no. There's some extra complexity with that, especially considering that values and pointers can also implement different interfaces (with the pointer type having a super set of them). Idiomatic Go values being explicit where possible, as explicit code is easier to reason about.
> This is filed to track the issue, and come to a long term decision on it. The first pass will not do so as it's simpler, but users may express a desire for this. It should be considered in the event that a user written work around no longer suffices.
>  
> Related: https://issues.apache.org/jira/browse/BEAM-3306
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)