Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/src/apimanual.md
Original file line number Diff line number Diff line change
Expand Up @@ -1069,7 +1069,7 @@ appropriate bridges for unsupported constrained variables.
A constraint can often be written in a number of equivalent formulations. For
example, the constraint ``l \le a^\top x \le u``
(`ScalarAffineFunction`-in-`Interval`) could be re-formulated as two
constraints: ``a^\top x ge l`` (`ScalarAffineFunction`-in-`GreaterThan`) and
constraints: ``a^\top x \ge l`` (`ScalarAffineFunction`-in-`GreaterThan`) and
``a^\top x \le u`` (`ScalarAffineFunction`-in-`LessThan`). An alternative
re-formulation is to add a dummy variable `y` with the constraints ``l \le y \le
u`` (`SingleVariable`-in-`Interval`) and ``a^\top x - y = 0``
Expand Down Expand Up @@ -1127,7 +1127,7 @@ MOI.set(model, MyPackage.PrintLevel(), 0)

### Supported constrained variables and constraints

The solver interface should only implement support for support for variables
The solver interface should only implement support for variables
constrained on creation (see
[`add_constrained_variable`](@ref)/[`add_constrained_variables`](@ref)) or
constraints that directly map to a structure exploited by the solver algorithm.
Expand Down
2 changes: 1 addition & 1 deletion src/variables.jl
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ end
"""
supports_add_constrained_variables(
model::ModelLike,
S::Type{<:AbstractScalarSet}
S::Type{<:AbstractVectorSet}
)::Bool

Return a `Bool` indicating whether `model` supports constraining a vector of
Expand Down