From 99bd6f7c15e397a5fba9a9aa958d6fb4b6e8751e Mon Sep 17 00:00:00 2001 From: Kinneyzhang Date: Mon, 27 Jul 2026 02:07:43 +0800 Subject: [PATCH] Drop tp-stack's phantom dependency on tp-ops tp-stack.el required tp-ops but used nothing from it: a whole-word sweep of every symbol tp-ops defines finds exactly one hit in tp-stack, and it is a docstring cross-reference to tp-set, not code. The require only made the module graph look denser than it is and suggested a stack->ops edge that never existed. The stack module's real dependencies are tp-core (interval walking), tp-reactive (the buffer registry it feeds via tp-reactive--register-layer-buffer) and tp-layer (the stack-storage codec). All three requires are already present, and tp-stack.el byte-compiles independently with warnings-as-errors after the deletion. Load order through tp.el is unaffected. Co-Authored-By: Claude Fable 5 --- tp-stack.el | 1 - 1 file changed, 1 deletion(-) diff --git a/tp-stack.el b/tp-stack.el index d406d1b..8fbeb74 100644 --- a/tp-stack.el +++ b/tp-stack.el @@ -22,7 +22,6 @@ (require 'tp-core) (require 'tp-reactive) (require 'tp-layer) -(require 'tp-ops) ;;; Shared argument parsing and region iteration