v1.0.6

Parsers v1.0.6

Diff since v1.0.5

Merged pull requests:

• Restrict main parsing to known supported types (#57) (@quinnj)

v1.0.5

Parsers v1.0.5

Diff since v1.0.4

Closed issues:

• Parsing float string as int fails to fail (#55)

Merged pull requests:

• Make sure Parsers.parse consume full input for non-IO arguments (#56) (@quinnj)

v1.0.4

Parsers v1.0.4

Diff since v1.0.3

Closed issues:

• "." is still parsed as 0.0 (#53)

Merged pull requests:

• Fix successful parsing of single decimal point as valid float (#54) (@quinnj)

v1.0.3

Parsers v1.0.3

Diff since v1.0.2

Merged pull requests:

• Ensure invalid dates follow Parsers error flow (#51) (@quinnj)
• Don't parse more digits that we know we'll need (#52) (@quinnj)

v1.0.2

Parsers v1.0.2

Diff since v1.0.1

v1.0.1

Parsers v1.0.1

Diff since v1.0.0

Merged pull requests:

• Don't treat "." as valid float (#50) (@quinnj)

v1.0.0

Parsers v1.0.0

Diff since v0.3.12

Closed issues:

• What's the advantage over Base.parse? (#47)

Merged pull requests:

• [BREAKING] Implement ignoreemptylines, commented line skipping, and ignorerepeated improvements (#48) (@quinnj)
• Bring ryu updates from Base here (#49) (@quinnj)

v0.3.12

v0.3.12 (2020-02-29)

Diff since v0.3.11

v0.3.11

v0.3.11 (2020-01-31)

Diff since v0.3.10

Closed issues:

• Int64 parsing error (#44)

Merged pull requests:

• fix Int64 parse error in case close to overflow (#44) (#45) (KlausC)

v0.3.10

v0.3.10 (2019-11-21)

Diff since v0.3.9

Merged pull requests:

• In roundQuotient, mod Int64 instead of using constructor to avoid Ine… (#43) (quinnj)