Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JuMP code to go with the MOI PR jump-dev/MathOptInterface.jl#1252.
If we lazily bridge the lazy bridges, we get much improved speed in the case that the user writes a model without bridges. (The first two benchmark calls.) This comes from avoiding a copy, and from not having to infer the bridging call-chain.
Importantly, because JuMP already has a
MOI.AbstractOptimizer
backend, there are no performance implications when bridges are used.For now I've just added a new function, but we could add this as opt-in to the standard
Model
constructor, and change it to the default in the next breaking JuMP release.Code