Skip to content

calling onOutput on a Workflow may never produce a value whose type can be inferred #284

Description

@jamieQ

for example, try splitting this expression into 2 parts. the compiler complains that the first expression's type is ambiguous without an annotation. it would be preferable if this behavior could be avoided.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions