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

IndexedVector doesn't work if Type isn't a Number #36

Closed
IainNZ opened this issue Sep 15, 2013 · 4 comments
Closed

IndexedVector doesn't work if Type isn't a Number #36

IainNZ opened this issue Sep 15, 2013 · 4 comments

Comments

@IainNZ
Copy link
Collaborator

IainNZ commented Sep 15, 2013

Makes collecting all variables coefficients together not work.

@mlubin
Copy link
Member

mlubin commented Sep 21, 2013

Could you give an example of how you'd like to use it?

@IainNZ
Copy link
Collaborator Author

IainNZ commented Sep 21, 2013

IndexedVector(GenericAffExpr{Float64, Uncertain}, m.numCols)
which I'd use for a
GenericAffExpr{GenericAffExpr{Float64, Uncertain}, Variable}

@mlubin mlubin closed this as completed in 027b672 Sep 21, 2013
mlubin added a commit that referenced this issue Sep 21, 2013
@mlubin
Copy link
Member

mlubin commented Sep 21, 2013

This should work now, you just need to implement zero(GenericAffExpr{Float64, Uncertain}) to return an empty expression. Don't forget to remove duplicates in each GenericAffExpr after you remove duplicates in the GenericAffExpr{GenericAffExpr} :)

@IainNZ
Copy link
Collaborator Author

IainNZ commented Sep 21, 2013

Oh happy day :)

mlubin added a commit that referenced this issue Mar 11, 2018
introduce a scope for user-defined functions
blegat pushed a commit that referenced this issue Oct 16, 2018
Check problem type after reading from file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants