Closed kit494way closed 10 months ago
This bug is introduced by this change #50. It seems that the rule, which parses a number omitted after decimal point (e.g. 1.) as float, parses head of range value as float incorrectly.
1.
oh, ya. good catch. i hadn't noticed this one.
This bug is introduced by this change #50. It seems that the rule, which parses a number omitted after decimal point (e.g.
1.
) as float, parses head of range value as float incorrectly.