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

Should support for MathOptInterface be moved to an extension? #203

Closed
palday opened this issue Aug 10, 2023 · 6 comments · Fixed by #204
Closed

Should support for MathOptInterface be moved to an extension? #203

palday opened this issue Aug 10, 2023 · 6 comments · Fixed by #204

Comments

@palday
Copy link
Contributor

palday commented Aug 10, 2023

Some examination of @time_imports for MixedModels.jl showed that MathOptInterface is one of our largest/slowest imports, even though we don't actually use and just use the NLopt 'native' interface.

I can do the legwork if this sounds reasonable.

cc @dmbates

@jw3126
Copy link

jw3126 commented Aug 12, 2023

Same here I want to solve a tiny problem that does not need MOI, yet right now it is a big precomilation and loading cost. BTW thanks for wrapping nlopt and creating it in the first place, this is awesome!

@stevengj
Copy link
Collaborator

Sounds good to me.

@mlubin
Copy link
Member

mlubin commented Aug 12, 2023

How can we do this without breaking JuMP+NLopt users on Julia pre 1.9? We need to support at least the latest LTS (1.6).

@palday
Copy link
Contributor Author

palday commented Aug 12, 2023

@mlubin one option would be to have this change be a breaking release that is otherwise compatible with the current release series but with a higher julia compat bound. Then it's straightforward to backport fixes, etc. and when the next LTS is declared, we drop support for the current series.

@palday
Copy link
Contributor Author

palday commented Aug 12, 2023

@blegat
Copy link
Member

blegat commented Aug 13, 2023

Then it's straightforward to backport fixes,

I wouldn't say that, it's best to keep the compatibility for v1.6 in master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

5 participants