Closed odow closed 2 months ago
I'm open to a discussion on whether this should be v0.16.3 or v0.17.0.
The argument for v0.17.0 is that it is a rather large change: https://github.com/jump-dev/Xpress.jl/compare/v0.16.2...master
The main breakage risks are #257 and #259.
64(
Lib
XPRSgetmipentities
XPRSgetglobal
I've also moved a bunch of unused stuff to src/api.jl which was never tested, so there's a risk I made a mistake during the refactoring that wasn't caught because of the lack of tests.
src/api.jl
Bump
Bump @joaquimg
I'm open to a discussion on whether this should be v0.16.3 or v0.17.0.
The argument for v0.17.0 is that it is a rather large change: https://github.com/jump-dev/Xpress.jl/compare/v0.16.2...master
The main breakage risks are #257 and #259.
259 is breaking for anyone using the
64(
functions inLib
(but they were probably already broken because of the wrong type?)257 has one breakage, removing https://github.com/jump-dev/Xpress.jl/blob/ceb9df83ff254db8684be77966ffd350321e07b8/src/Lib/xprs.jl#L2366-L2394 You now must explicitly call
XPRSgetmipentities
orXPRSgetglobal
, but this shouldn affect only people hacking at the C API.I've also moved a bunch of unused stuff to
src/api.jl
which was never tested, so there's a risk I made a mistake during the refactoring that wasn't caught because of the lack of tests.TODO