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

Rework parameters/returns #63

Open
robrix opened this issue Mar 30, 2015 · 2 comments
Open

Rework parameters/returns #63

robrix opened this issue Mar 30, 2015 · 2 comments

Comments

@robrix
Copy link
Contributor

robrix commented Mar 30, 2015

They should be inputs/outputs of a special graph identifier. We would unfortunately have to communicate the initial type to be constrained & solved for extrinsically.

@robrix
Copy link
Contributor Author

robrix commented Apr 13, 2015

Identifiers are no longer a thing, but it’d still be nice to find a graph’s returns and parameters under a specific “blessed” index.

We could use endIndex, except that we’d have to do an O(n) search through the edges and update any pointing at it every time we add a node.

@robrix
Copy link
Contributor Author

robrix commented Apr 13, 2015

An alternative would be to replace Node.Parameter and Node.Return with Node.Graph. This would give us a place to encapsulate the parameters, the returns, the type, even the name.

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