Eric Hanson

I'm starting to see how this can all work together. This rewrite is actually not very different than how Convex.jl works now, but I think will actually end up a...

I’m gonna leave this for now; I had it timeboxed to a week and couldn’t push it through but I think the idea works (the idea is very simple, mostly...

Just had a stray thought for how to do the hashing for deeply nested trees that repeat themselves. Currently we can have hash collisions (#78) and the hashing step can...

> https://github.com/jump-dev/ComplexOptInterface.jl I did see that, but it was/is still pretty early for that effort. My thought in this PR was to just continue supporting complex variables for the current...

Something related we should consider is how the user passes the solver. The problem is this: on the current MOI PR branch, if the user writes ```julia using Convex, SDPA...

As was mentioned in https://github.com/JuliaOpt/Convex.jl/issues/354, we should consider how the users interact with the termination statuses as well. (And at least document it). It would be nice also if we...

I think the solution for `Variable` field access is https://github.com/JuliaOpt/Convex.jl/pull/313; introducing a full `AbstractVariable` interface is a bit more than we need, but I think it's quite nice and also...

Looks like https://github.com/JuliaOpt/MathOptInterface.jl/pull/1008 might help with the solver interface problem discussed above

@dstahlke welcome to Julia :). I have not tried out your code but I will probably have time to do so next week. What kinds of problems are you interested...

MathOptInterface (MOI) is an intermediary layer that sits between Convex.jl and the underlying solvers (SCS, Mosek, etc). The job of MathOptInterface is that if a solver does not support a...