Bump sled from 0.30.3 to 0.32.0

[dependabot-preview[bot]]

Bumps sled from 0.30.3 to 0.32.0.

Release notes

Sourced from sled's releases.

0.32

New Features

• #1079 Transactional is now implemented for [&Tree] and [Tree] so you can avoid the previous friction of using tuples, as was necessary previously.
• #1058 The minimum supported Rust version (MSRV) is now 1.39.0.
• #1037 Subscriber now implements Future (non-fused) so prefix watching may now be iterated over via while let Some(event) = (&mut subscriber).await {}

Improvements

• A large number of crash consistency issues have been discovered during intensive testing and fixed.
• #965 concurrency control is now dynamically enabled for atomic point operations, so that it may be avoided unless transactional functionality is being used in the system. This significantly increases performance for workloads that do not use transactions.
• A number of memory optimizations have been implemented.
• Disk usage has been significantly reduced for many workloads.
• #1016 On 64-bit systems, we can now store 1-2 trillion items.
• #993 Added DerefMut and AsMut for IVec where it works similarly to a Cow, making a private copy if the backing Arc's strong count is not 1.
• #1020 The sled wiki has been moved into the documentation itself, and is accessible through the doc module exported in lib.

Breaking Changes

• #975 Changed the default segment_size from 8m to 512k. This will result in far smaller database files due to better file garbage collection granularity.
• #975 deprecated several Config options that will be removed over time.
• #1000 rearranged some transaction-related imports, and moved them to the transaction module away from the library root to keep the top level docs clean.
• #1015 TransactionalTree::apply_batch now accepts its argument by reference instead of by value.
• Event has been changed to make the inner fields named instead of anonymous.
• #1057 read-only mode has been removed due to not having the resources to properly keep it tested while

Changelog

Sourced from sled's changelog.

0.32

New Features

• #1079 Transactional is now implemented for [&Tree] and [Tree] so you can avoid the previous friction of using tuples, as was necessary previously.
• #1058 The minimum supported Rust version (MSRV) is now 1.39.0.
• #1037 Subscriber now implements Future (non-fused) so prefix watching may now be iterated over via while let Some(event) = (&mut subscriber).await {}

Improvements

• #965 concurrency control is now dynamically enabled for atomic point operations, so that it may be avoided unless transactional functionality is being used in the system. This significantly increases performance for workloads that do not use transactions.
• A number of memory optimizations have been implemented.
• Disk usage has been significantly reduced for many workloads.
• #1016 On 64-bit systems, we can now store 1-2 trillion items.
• #993 Added DerefMut and AsMut for IVec where it works similarly to a Cow, making a private copy if the backing Arc's strong count is not 1.
• #1020 The sled wiki has been moved into the documentation itself, and is accessible through the doc module exported in lib.

Breaking Changes

• #975 Changed the default segment_size from 8m to 512k. This will result in far smaller database files due to better file garbage collection granularity.
• #975 deprecated several Config options that will be removed over time.
• #1000 rearranged some transaction-related imports, and moved them to the transaction module away from the library root to keep the top level docs clean.
• #1015 TransactionalTree::apply_batch now accepts its argument by reference instead of by value.
• Event has been changed to make the inner fields named instead of anonymous.
• #1057 read-only mode has been removed due to not having the resources to properly keep it tested while making progress on high priority issues. This may

Commits

• See full diff 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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)