As @andreab1997 detected: when evolving with an EKO which is all 0s (by mistake) this results in an invalid FK table with no orders (and so the NonTrivialOrder error is returned). The new evolve somewhere discards operators which are 0 everywhere to gain speed - this is just fine.
However, if the EKO is all 0s we should either complain (maybe preferred) or return a valid FK table which is 0 everywhere.
As @andreab1997 detected: when evolving with an EKO which is all 0s (by mistake) this results in an invalid FK table with no orders (and so the
NonTrivialOrder
error is returned). The newevolve
somewhere discards operators which are 0 everywhere to gain speed - this is just fine.However, if the EKO is all 0s we should either complain (maybe preferred) or return a valid FK table which is 0 everywhere.