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

segregate scalar and vector sets and functions #64

Merged
merged 1 commit into from
Jul 19, 2017
Merged

Conversation

mlubin
Copy link
Member

@mlubin mlubin commented Jul 19, 2017

Trying this out to see if it's a useful concept. Is it the case that we would only want to allow constraints of the form "vector-valued function" in "vector-input set" and "scalar-valued function" in "scalar-input set"?

This is a revival and extension of @blegat's #44.

@mlubin mlubin force-pushed the ml/scalarvector branch from 2c9158c to a4ca377 Compare July 19, 2017 07:24
@mlubin mlubin force-pushed the ml/scalarvector branch from a4ca377 to 63aab8a Compare July 19, 2017 07:31
@blegat
Copy link
Member

blegat commented Jul 19, 2017

We could also do it for function modification : AbstractScalarFunctionModification and AbstractVectorFunctionModification.

@mlubin
Copy link
Member Author

mlubin commented Jul 19, 2017

@blegat, makes sense. I'll leave that for a separate PR.

@mlubin mlubin merged commit 9aad2e5 into master Jul 19, 2017
@mlubin mlubin deleted the ml/scalarvector branch July 19, 2017 14:17
@mlubin mlubin mentioned this pull request Jul 21, 2017
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants