Replace lockfree with lock_freedom

[jayvdb]

c.f. rustsec/advisory-db#2461

Note I wasnt able to compile on either my macos intel or linux intel, even when trying to disable features and only enable the lockfree feature. I can write up issues about these if you would find that useful.

Summary by CodeRabbit

• Chores
  • Updated internal dependency for lock-free structures functionality, including version adjustments and corresponding documentation updates.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The dependency lockfree (version 0.5) is updated to use the external package lock_freedom (version 0.1.1) in Cargo.toml, with corresponding documentation changes reflecting the new dependency in the implementation guide.

Changes

Cohort / File(s)	Summary
Dependency declaration update Cargo.toml	Updated lockfree dependency to use lock_freedom package (v0.1.1) instead of v0.5; crate remapped with package attribute
Documentation update docs/implementation.md	Updated dependencies snippet to reference lock_freedom = "0.1" instead of lockfree = "0.5"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Straightforward dependency version and package name substitution across two files
• No logic changes or API surface modifications
• Documentation remains consistent with code changes

Poem

🐰 A lock-freedom dance, new and bright,
Version zero-one takes flight,
From 0.5 we bid adieu,
Fresh dependencies, shiny and new! 🔐

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Replace lockfree with lock_freedom' is fully related to the main change in the changeset, accurately summarizing the dependency replacement across both Cargo.toml and documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5bfb185 and 0c0ccb1.

📒 Files selected for processing (2)

• Cargo.toml (1 hunks)
• docs/implementation.md (1 hunks)

🔇 Additional comments (1)

Cargo.toml (1)

44-44: The external lockfree crate is unused; review concerns are not applicable.

Verification shows that the external lockfree 0.5 crate was never actually used in the codebase. All references to "lockfree" are to the internal module in src/lockfree.rs, which contains custom implementations (LockFreePageCache, LockFreeIoQueue, etc.). No code imports or calls the external crate's API, and there are no feature-gated compilation paths depending on it.

Since the dependency was dormant, replacing it with lock_freedom 0.1.1 has no practical impact. The concerns about API compatibility and resolving compilation issues do not apply.

Likely an incorrect or invalid review comment.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Update documentation to match Cargo.toml version specification.

The documentation specifies lock_freedom = "0.1", but Cargo.toml specifies version "0.1.1". For clarity and consistency, update the documentation to reflect the exact version constraint.

-lock_freedom = "0.1"
+lock_freedom = "0.1.1"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	lock_freedom = "0.1"
	lock_freedom = "0.1.1"

🤖 Prompt for AI Agents

In docs/implementation.md around line 503, the documented dependency version is
shown as lock_freedom = "0.1" which does not match Cargo.toml's "0.1.1"; update
the documentation to use the exact version string used in Cargo.toml
(lock_freedom = "0.1.1") so the docs and manifest are consistent.

[jayvdb]

ping @niklabh