Walkthrough

Workspace-wide dependency version bumps and additions, several crate Cargo.toml dependency removals/relocations, and benchmark updates replacing pyo3::Python::with_gil with pyo3::Python::attach and using std::hint::black_box; no public API changes.

Changes

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Bench as Benchmark
  participant PyO3 as pyo3
  participant GIL as GIL
  participant VM as Python_VM

  Note over Bench,PyO3: New flow uses Python::attach for GIL scope
  Bench->>PyO3: Python::attach(|py| { ... })
  activate PyO3
  PyO3->>GIL: attach current thread (GIL acquired)
  activate GIL
  GIL->>VM: compile & execute Python code
  VM-->>GIL: result / error
  deactivate GIL
  PyO3-->>Bench: closure returns with result
  deactivate PyO3

  Note over Bench: Measurements use std::hint::black_box for isolation

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Update some deps #6053 — Overlapping workspace dependency version bumps (e.g., bitflags, indexmap).
• Switch to newer thread::LocalKey convenience methods #6123 — Related changes touching thread/GIL handling patterns and bench adjustments.

Suggested reviewers

• youknowone

Poem

A nibble of deps, a hop through the bench,
I attach to the GIL with a whisker’s clench.
Black boxes hush what numbers reveal—
Versions align, the wheels all wheel.
Tap-tap my paw: cargo says “go!” 🐇✨

Pre-merge checks and finishing touches

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

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