Volker
Volker
Confirmed that this issue is still present in boost 1.72.0. Looking forward to the next milestone!
Confirming that this issue is still present in boost 1.73.0. Looking forward to the next milestone!
Confirming that this issue is still present in boost 1.75.0. Looking forward to the next milestone!
@vissarion Thank you for looking into this. I'll check as soon as we update our boost library (we'll wait for 1.80 because there will be another fix we need), and...
> @vschoech is this still present in 1.79.0 (rescaling is removed). We updated our code base to 1.79 and I can now confirm that this issue is still present.
As of boost 1.72.0, this problem is still present as reported!
As of boost 1.73.0, this problem is still present as reported!
Confirming that this issue is still present in boost 1.75.0. Looking forward to the next milestone!
Confirming that this issue is still present in boost 1.79.0. Looking forward to the next milestone!
The problem is still not fixed in boost 1.73.0.