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.

Sign up for GitHub

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

Jump to bottom

Consider bridging lambdas the same way we bridge Flow #1495

Open
JakeWharton opened this issue Jan 8, 2025 · 0 comments
Open

Consider bridging lambdas the same way we bridge Flow #1495

JakeWharton opened this issue Jan 8, 2025 · 0 comments
Labels
enhancement PR welcome

Comments

@JakeWharton
Copy link
Collaborator

Today you have to use a named type which extends from ZiplineService, but we could automatically bridge the lambda itself and now only the lambda parameters and return type would be constrained by the need to be serializable (or ZiplineServices).

Can lambda Function be implemented internal zipline in a way similar to Flow?

Originally posted by @qhyuan1992 in #1494 (reply in thread)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement PR welcome
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JakeWharton