Bump lexical-core from 0.8.5 to 1.0.0

[dependabot]

Bumps lexical-core from 0.8.5 to 1.0.0.

Release notes

Sourced from lexical-core's releases.

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.

Removed

• Support for mips (MIPS), mipsel (MIPS LE), mips64 (MIPS64 BE), and mips64el (MIPS64 LE) on Linux.
• All _unchecked API methods, since the performance benefits are dubious and it makes safety invariant checking much harder.
• The safe and nightly features, since ASM is now supported by the MSRV on stable and opt-in for memory-safe indexing is no longer relevant.

Lexical-Core Version 0.8.6 Release

Changed

• Fixed partial integer parser to correct return negative values.

Changelog

Sourced from lexical-core's changelog.

[1.0.0] 2024-09-16

Changed

• Fixes a correctness regression

[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.
• Writing special numbers even with invalid float formats is now always memory safe.

Removed

• Support for mips (MIPS), mipsel (MIPS LE), mips64 (MIPS64 BE), and mips64el (MIPS64 LE) on Linux.
• All _unchecked API methods, since the performance benefits are dubious and it makes safety invariant checking much harder.
• The safe and nightly features, since ASM is now supported by the MSRV on stable and opt-in for memory-safe indexing is no longer relevant.

Commits

• 7c0100d Merge pull request #135 from Alexhuszagh/writesafe
• 7df1e74 Make clippy happy (they deserve it).
• 0970a59 Merge pull request #134 from Alexhuszagh/security
• f99c862 Create SECURITY.md
• 70cc557 Do more housekeeping for documentation.
• c6f69e3 Remove modules with unused features.
• a2667d5 Complete our safety mitigations in the float writers.
• a7d9583 Remove all unsafety in our float writers.
• a2434f0 Minor refactoring that mostly improves performance.
• b2da5f5 Remove further unsafety from the overall API.
• 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.