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

Model evaluation of graphs with multiple returns #3

Open
robrix opened this issue Dec 28, 2014 · 2 comments
Open

Model evaluation of graphs with multiple returns #3

robrix opened this issue Dec 28, 2014 · 2 comments

Comments

@robrix
Copy link
Contributor

robrix commented Dec 28, 2014

Specifically, the semantics must avoid redundant computation of shared dependencies. For example, if we had two inputs, a and b, and returned two values, a + b - a and a + b - b, a + b must be computed exactly once.

@robrix
Copy link
Contributor Author

robrix commented Feb 1, 2015

Currently I’m thinking of a graph with n returns as n functions (at least externally).

@robrix
Copy link
Contributor Author

robrix commented Mar 30, 2015

This would be greatly simplified by #29. By-need evaluation means that a graph with multiple returns has a product return type, and we only compute the fields which we project out of it.

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

No branches or pull requests

1 participant