Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
jamieQ opened this issue Jun 14, 2024 · 0 comments

Comments

@jamieQ
Copy link
Contributor

jamieQ commented Jun 14, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant