Oscar Dowson

Let's table this question until we have `ScalarNonlinearFunction` support. For now we won't be modifying the `@NLconstraint` macro because we don't want to be locked into supporting the syntax going...

We're fairly close with this: ```julia julia> using JuMP, MiniZinc julia> model = GenericModel{Int}(() -> MiniZinc.Optimizer{Int}("chuffed")) A JuMP Model Feasibility problem with: Variables: 0 Model mode: AUTOMATIC CachingOptimizer state: EMPTY_OPTIMIZER...

We also want `@constraint(model, x[1] || x[2] == x[3])` and we want it parsed as `@constraint(model, (x[1] || x[2]) == x[3])` (if possible)

> this functionality should ideally be incorporated into JuMP. An open question is whether we should vendor some form of UnitJuMP in as a JuMPExtension within JuMP, or whether we...

This is potentially a good candidate for the new `weakdeps` extension packages that are landing in Julia 1.9: https://pkgdocs.julialang.org/dev/creating-packages/#Conditional-loading-of-code-in-packages-(Extensions) We could move UnitJuMP to `/ext/UnitfulExt.jl`, and then if someone goes...

I took another look at this. I'm going to close as won't-fix. Supporting views of containers has a number of technical challenges (hard to add without breaking existing code) and...

Reopening because we need to make this work for https://github.com/jump-dev/JuMP.jl/issues/3151.

`view` is now supported for `DenseAxisArray`. I don't know if there's an easy way to make it work for `SparseAxisArray` (you can't call `view` on a dictionary), so I'm inclined...

#3184 resolves another array-in-scalar-set issue. But I'm not convinced about changing the vector-valued sets. It seems ripe to add more confusion, rather than less. People can easily do things like...

@blegat are you okay with closing this? > it should not be too confusing once the user gets used to it. I'm not convinced that the syntax: ```julia @variable(model, x[1:2,...