Fixes potentially outdated value of getVal

[mmghannam]

Without this, the value could be outdated as it depends on calling getBestSol before.

[Joao-Dionisio]

Can you add a test that fails without this, please?

I'm a bit worried about scripts that call getVal very often, though. Sure, it's a tiny tiny additional effort, but people using things like getVarDict on big models might feel the difference. We would be creating a Solution object for every variable.

Can we somehow circumvent this? A terrible idea I just had was to attach an even handler to every model, that catches BESTSOLFOUND and the execmethod calls getBestSol.

[Joao-Dionisio]

This is cracking me up. If not raise error, then raise value error.
We were the ones who added this, Mo ahah

[mmghannam]

Can you add a test that fails without this, please?

I'm a bit worried about scripts that call getVal very often, though. Sure, it's a tiny tiny additional effort, but people using things like getVarDict on big models might feel the difference. We would be creating a Solution object for every variable.

Can we somehow circumvent this? A terrible idea I just had was to attach an even handler to every model, that catches BESTSOLFOUND and the execmethod calls getBestSol.

We could maybe prevent it in the solving stage, and raise and error guiding the user to the other methods.