Bump lexical-core from 0.8.5 to 1.0.2

[dependabot]

Bumps lexical-core from 0.8.5 to 1.0.2.

Release notes

Sourced from lexical-core's releases.

Version 1.0.2 Release

Changed

• Higher performance when parsing floats with digit separators.

Fixed

• Inlining inconsistency between public API methods (credit to @​zheland)
• Incorrectly accepting leading zeros when no_integer_leading_zeros was enabled.
• Have consistent errors when an invalid leading digit is found for floating point numbers to always be Error::InvalidDigit.
• Incorrect parsing of consecutive digit separators.
• Inaccuracies when parsing digit separators at various positions leading to incorect errors being returned.
• Selecting only a subset of parse and/or write features would cause compilation errors.
• Fixed bug with writing integers with custom radices.

Version 1.0.1 Release

Fixed

• A correctness regression.
• Regressions where parsing digit separators without the compact panicked.

v1.0.0 Release

The full changelog is as follows:

Added

• Added fuzzing and miri code safety analysis to our CI pipelines.
• Removed requirement of alloc in no_std ennvironments without the write feature.
• Make multi-digit optimizations in integer parsing optional.
• Much higher miri coverage including for proptests and our corner cases from the golang test suite.

Changed

• Updated the MSRV to 1.63.0 (1.65.0 for development).
• Improved performance due to compiler regressions in rustc 1.81.0 and above.

Fixed

• Removed use of undefined behavior in MaybeUninit.
• Provide better safety documentation.
• Parsing of Ruby float literals.
• Performance regressions in Rust 1.81.0+.
• Removed incorrect bounds checking in reading from iterators.
• Overflow checking with integer parsing.
• Writing -0.0 with a leading -.
• Reduced binary siezes when the compact feature was enabled.
• Improved performance of integer and float parsing, particularly with small integers.
• Removed almost all unsafety in lexical-util and clearly documented the preconditions to use safely.
• Removed almost all unsafety in lexical-write-integer and clearly documented the preconditions to use safely.
• Writing special numbers even with invalid float formats is now always memory safe.

... (truncated)

Changelog

Sourced from lexical-core's changelog.

[1.0.2] 2024-09-24

Changed

• Higher performance when parsing floats with digit separators.

Fixed

• Inlining inconsistency between public API methods (credit to @​zheland)
• Incorrectly accepting leading zeros when no_integer_leading_zeros was enabled.
• Have consistent errors when an invalid leading digit is found for floating point numbers to always be Error::InvalidDigit.
• Incorrect parsing of consecutive digit separators.
• Inaccuracies when parsing digit separators at various positions leading to incorect errors being returned.
• Selecting only a subset of parse and/or write features would cause compilation errors.
• Fixed bug with writing integers with custom radices.

[1.0.1] 2024-09-16

Fixed

• A correctness regression.
• Regressions where parsing digit separators without the compact panicked.

[1.0.0] 2024-09-14

Added

• Added fuzzing and miri code safety analysis to our CI pipelines.
• Removed requirement of alloc in no_std ennvironments without the write feature.
• Make multi-digit optimizations in integer parsing optional.
• Much higher miri coverage including for proptests and our corner cases from the golang test suite.

Changed

• Updated the MSRV to 1.63.0 (1.65.0 for development).
• Improved performance due to compiler regressions in rustc 1.81.0 and above.

Fixed

• Removed use of undefined behavior in MaybeUninit.
• Provide better safety documentation.
• Parsing of Ruby float literals.
• Performance regressions in Rust 1.81.0+.
• Removed incorrect bounds checking in reading from iterators.
• Overflow checking with integer parsing.
• Writing -0.0 with a leading -.
• Reduced binary siezes when the compact feature was enabled.
• Improved performance of integer and float parsing, particularly with small integers.
• Removed almost all unsafety in lexical-util and clearly documented the preconditions to use safely.
• Removed almost all unsafety in lexical-write-integer and clearly documented the preconditions to use safely.

... (truncated)

Commits

• 6ab9853 Increment lexical dependency.
• 8282e24 Fix write float version.
• 33c6ed3 Fix parse float version.
• 0219b22 Increment versions for release.
• 145efa5 Merge pull request #162 from Alexhuszagh/feature_check
• dfad54f Add patches for feature configurations and serializing radices.
• f6d943c Update README for customization.
• eb3eb29 Merge pull request #161 from Alexhuszagh/issue_96
• df828cd Improve the formatting API.
• c102122 Merge pull request #160 from Alexhuszagh/deny_lint
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[jaychia]

@colin-ho let's see if this might be an easy fix/upgrade for us? If not we can skip this upgrade.

[dependabot]

Superseded by #3531.