Mathieu Besançon

hi, no in fact we would keep a storage I believe, but not assume the grad! function returns it, so you would have something like ```julia # out of place...

the second version would be to have everything out of place, but then users would need to set up a closure and workspace to make it efficient and that's too...

yes exactly. The point is that some procedures will perform an out of place anyway so forcing the API to be in-place only doesn't make sense

I agree it would be great to have an explanation for each of them. Not sure whether the docstring or the docs directly would be better as a location

> especially the projections we might need for bcg or if we want to add fcfw so you mean for this using JuMP as a sub-solver for LMO?

@alejandro-carderera that's the paper we mentioned in the call

The Greedy Convex Ensemble from above

looking quickly at the paper, doesn't this need new LMOs?

@pokutta I think you have merged this into another branch that got merged into master, it is already there - it is not quite ready because of the interfacing as...

yes this one was postponed, the phi could be placed in the CachingLMO but there are some things in printing that are custom and a bit of a pain to...