Michael Bynum

We could support this if we identified common expressions, forming a single DAG for the entire problem. It should be doable, and is a feature worth having.

I've created an issue in the HiGHS repo for this (https://github.com/ERGO-Code/HiGHS/issues/1386).

@ZedongPeng, Can you pinpoint exactly when HiGHS outputs this? I don't think it is during `run`. Maybe when the HiGHS model is constructed?

I only think we should hide the output after it is displayed at least once.

Well said, @Robbybp

I think we should move this method into a "helper function" that takes in a model and a solver and modifies both. This way, we maintain that solver interfaces do...

This could be done on the c++ side by creating a new solution object for the python interface, but it would still require copying the std::vectors into arrays. That is...

Please assign me.

Yes, I believe releasing the GIL will also fix the keyboard interrupt issue.

I did try to fix this, but my initial attempt was not successful. I'll give it another try today.