You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/08/09 17:22:01 UTC
[jira] [Commented] (BEAM-12413) Type inference works incorrectly
with tuple slices
[ https://issues.apache.org/jira/browse/BEAM-12413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396174#comment-17396174 ]
Beam JIRA Bot commented on BEAM-12413:
--------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.
> Type inference works incorrectly with tuple slices
> --------------------------------------------------
>
> Key: BEAM-12413
> URL: https://issues.apache.org/jira/browse/BEAM-12413
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Dmytro Kozhevin
> Priority: P3
>
> Returning a slice of the tuple doesn't alter the type inference output. For example:
>
> {{@beam.typehints.with_output_types(Tuple[int, str])}}
> {{class Foo(beam.DoFn):}}
> {{ def process(self, a):}}
> {{ yield a, str(a)}}
> {{pcoll = beam.Pipeline() }}| beam.Create([1]) | beam.ParDo(Foo()) | beam.Map(lambda x: x[1:])
> {{print(pcoll.element_type)}}
>
> This prints Tuple[int, str], while the real type is str. At worst, this should return Any.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)