transform-tree 0.0.3__tar.gz → 0.0.4__tar.gz

{transform_tree-0.0.3 → transform_tree-0.0.4}/Cargo.toml

@@ -45,7 +45,7 @@ exclude = [
 # an MSRV raise reaches nobody who did not opt into it by editing a manifest.
 # The rule comes back into force at 0.1.0, where a minor slot exists again.
 # `SUPPORT.md`'s MSRV section carries the same statement in its own voice.
-version = "0.0.3"
+version = "0.0.4"
 edition = "2021"
 # **1.87, and each step was forced by a dependency rather than chosen.**
 #
@@ -122,8 +122,8 @@ unexpected_cfgs = { level = "warn", check-cfg = ['cfg(loom)'] }
 [workspace.dependencies]
 # Intra-workspace crates (version pinned so publishable crates carry a real
 # requirement, not a path wildcard).
-tf_tree_math = { path = "crates/tf_tree_math", version = "0.0.3" }
-tf_tree_arena = { path = "crates/tf_tree_arena", version = "0.0.3" }
+tf_tree_math = { path = "crates/tf_tree_math", version = "0.0.4" }
+tf_tree_arena = { path = "crates/tf_tree_arena", version = "0.0.4" }
 # Phase 2 shared memory (see docs/PHASE2.md §2). Linux-only, opt-in via the
 # `shm` feature; `linux_raw` backend so there is no libc crate and no C build.
 # Only `tf_tree_ipc`, and only for `fcntl(F_OFD_*)`: rustix has no OFD locking
@@ -138,9 +138,9 @@ rustix = { version = "1.1", default-features = false, features = ["mm", "fs", "s
 # measurement — the "counters off" row was measuring the counters-on engine.
 # Every crate that wants them re-enables them through its own `counters`
 # feature, which is what makes the switch actually switch.
-tf_tree_core = { path = "crates/tf_tree_core", version = "0.0.3", default-features = false }
-tf_tree_ipc = { path = "crates/tf_tree_ipc", version = "0.0.3" }
-tf_tree = { path = "crates/tf_tree", version = "0.0.3", default-features = false }
+tf_tree_core = { path = "crates/tf_tree_core", version = "0.0.4", default-features = false }
+tf_tree_ipc = { path = "crates/tf_tree_ipc", version = "0.0.4" }
+tf_tree = { path = "crates/tf_tree", version = "0.0.4", default-features = false }
 # publish = false crates, wired by path only (no version requirement published).
 # **`default-features = false` for the same load-bearing reason as `tf_tree`
 # above, and it is easy to miss here.** `tf_tree_bench` has its own

{transform_tree-0.0.3 → transform_tree-0.0.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: transform_tree
-Version: 0.0.3
+Version: 0.0.4
 Classifier: Development Status :: 3 - Alpha
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.13

{transform_tree-0.0.3 → transform_tree-0.0.4}/crates/tf_tree/Cargo.toml

@@ -75,12 +75,31 @@ shm = ["tf_tree_arena/shm", "dep:tf_tree_ipc"]
 # rustdoc — but it is no longer the only thing standing between this feature
 # split and a compile error nobody sees.
 unstable = []
-# A single injection point inside `Tree::claim`, between the arena CAS and the
-# lease `SETLK` (`docs/decisions/0005` §5). Off by default and absent from the
-# API entirely unless enabled: the window it exposes is one syscall wide and
-# there is no other way to place a reaper inside it deterministically, but a
-# published hook that runs arbitrary code mid-claim is not something a shipped
-# build should carry. Enabled by `just shm-rendezvous`.
+# **Two seams a test cannot otherwise stand in.** Off by default and absent from
+# the API entirely unless enabled; both are `#[doc(hidden)]`.
+#
+# 1. `CLAIM_WINDOW_HOOK` — a single injection point inside `Tree::claim`,
+#    between the arena CAS and the lease `SETLK` (`docs/decisions/0005` §5). The
+#    window it exposes is one syscall wide and there is no other way to place a
+#    reaper inside it deterministically, but a published hook that runs
+#    arbitrary code mid-claim is not something a shipped build should carry.
+# 2. `reclamation_verdict_for_test` — `docs/decisions/0028` plan step 2's
+#    reclamation predicate, which is private and whose two production callers
+#    both act on a verdict without reporting one: the owner's slot assigner
+#    (that record's step 3) stops at the first grantable slot, and
+#    `Tree::reap_participants` (step 5) reports a slot count — so `Live` and
+#    `Unknown`, the two verdicts that collect nothing for opposite reasons, are
+#    indistinguishable through either. The five multiprocess tests around it
+#    turn on facts
+#    only the kernel produces (a `SIGSTOP`ped process keeps its lock byte, a
+#    `SIGKILL`ed one loses it, a read-only joiner holds one and writes no arena
+#    record), so they cannot be unit tests inside the crate, and nothing outside
+#    it can name a private function. The same feature adds the probe counter the
+#    seam reports, which is the only part of the predicate's read order a
+#    multiprocess test can observe.
+#
+# Enabled by `just shm-rendezvous`, and linted by `just shm-check`'s
+# `--features shm,test-hooks,unstable` clippy pass.
 test-hooks = []
 
 [dependencies]

{transform_tree-0.0.3 → transform_tree-0.0.4}/crates/tf_tree/README.md

@@ -115,11 +115,13 @@ exception — it is a private read-only mapping and a child inherits it intact.
 
 ## Version
 
-**0.0.1, and `0.0.x` promises nothing.** Cargo treats every `0.0.x` release as
+**`0.0.x` promises nothing.** Cargo treats every `0.0.x` release as
 incompatible with every other — `tf_tree = "0.0.1"` means `^0.0.1`, which
 matches `0.0.1` and nothing else — so a later release reaches no existing
-dependant through `cargo update`. That is the intended signal for a first
-publish: pin exactly, and expect a later release to break. The reasoning is
+dependant through `cargo update`. That is the intended signal: pin exactly, and
+expect a later release to break. The current number is deliberately not repeated
+here — this line said `0.0.1` for three releases, because nothing gates a
+version in prose. The reasoning is
 written out in the repository's
 [`Cargo.toml`](https://github.com/NoeFontana/tf_tree/blob/main/Cargo.toml) under
 `[workspace.package] version`, and the release notes are in

{transform_tree-0.0.3 → transform_tree-0.0.4}/crates/tf_tree/src/lib.rs

@@ -315,6 +315,18 @@ mod open;
 #[cfg(all(feature = "shm", target_os = "linux"))]
 pub use open::{open, CreatePolicy, Open, OpenError};
 
+/// Test scaffolding for `docs/decisions/0028` plan step 2's reclamation
+/// predicate, which is private. Its two production callers are the owner's
+/// slot assigner (that record's step 3) and [`Tree::reap_participants`] (step
+/// 5); both act on the verdict without reporting one — the assigner stops at
+/// the first grantable slot, the sweep reports a count — and neither a grant
+/// nor a count can separate the two verdicts that collect nothing. Absent
+/// unless `--features test-hooks`; see
+/// [`open::reclamation_verdict_for_test`].
+#[cfg(all(feature = "test-hooks", feature = "shm", target_os = "linux"))]
+#[doc(hidden)]
+pub use open::reclamation_verdict_for_test;
+
 /// **The unstable tier — `docs/API.md` §2.6.** Enabling the `unstable` feature
 /// is the waiver; read the module's own documentation for what it waives.
 #[cfg(feature = "unstable")]