CronExpression.ToString is not parseable anymore about cronos HOT 1 CLOSED

It looks like ToString() returns a cronexpression with seconds, hence the extra 0 in front. It looks like internally the fact that seconds were not included in the cronexpression parsed is not stored hence upon returning the ToString() it is not possible to differentiate between no seconds supplied and 0 seconds, which results in the 0 in the result.

P.S. The current implementation is not wrong, it might however be unexpected.
P.P.S. It is a different matter whether you want the exact same syntax back */5 instead of 0,5,10,15,20,25,30,35,40,45,50,55 which is again a decision, both express the same cronexpression.
P.P.P.S. Optimizing for ToString() speed is again, another matter and a separate thing from what should be returned from ToString() Since the implementation already does some bit-shift magic and explicitly mention storage bit sizes I guess someone might object to any bytes of additional memory consumed for optimizing ToString()

@odinserj If replies like this are not appreciated please say so. I was not trying to give opinionated answers or comments

from cronos.