Oscar Dowson
Oscar Dowson
> One reason we don't go to the effort of doing things like creating maintenance branches I'd say the bigger reason is that you don't have the labor available to...
The current binaries are not maintained by the core HiGHS team. We dynamically link things for use in Julia, but these binaries can also be used outside of Julia. Do...
> Do you only want static windows binaries? I meant, is your application distributed on Windows only, or do you also ship macOS and linux?
> hence the reason we deploy with the pre-compiled Windows binaries prepared by the other solvers. How does this work if you deploy GPL solvers like GLPK? Our static build...
The current binaries are compiled primarily for HiGHS.jl in Julia and made available for wider use. Notably, they aren't maintained or distributed by the official HiGHS team, and we don't...
The JuMP example is ```Julia @testset "$(file)" for file in filter(f -> endswith(f, ".jl"), readdir(@__DIR__)) # current @testset "$(file)" for file in filter(f -> endswith(f, ".jl"), readdir(@__DIR__)) @test 1 ==...
Our goal has been the fewer special the better, and special cases only with well justified reasoning.
If you're going to make it a standard, we can support `return nothing` instead of `return`. Is there a way (or any interest in adding a way) to do this...
No, once it gets to `s3` it stops.
What is `tmp`? You can't call `logsumexp` outside JuMP macros: https://discourse.julialang.org/t/how-to-implment-logsumexp-function-in-jump/84376/2