From 5a0274f3ebdb0830d3c43b07742c4911cd147358 Mon Sep 17 00:00:00 2001 From: David Meister Date: Mon, 21 Sep 2026 11:24:44 +0000 Subject: [PATCH] docs: drop the occupant-identity claim from CloneAddressOccupied The error is declared at file scope, so it is in every factory's ABI, and `cloneAndInitialize` bubbles a failing `initialize`'s revert data verbatim. A caller cannot tell the library's own throw from one a clone authored, so neither the selector nor the `clone` it carries identifies the occupant of anything. Co-Authored-By: Claude Opus 5 (1M context) --- src/lib/LibICloneableFactoryV4.sol | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/lib/LibICloneableFactoryV4.sol b/src/lib/LibICloneableFactoryV4.sol index f86a641..268715e 100644 --- a/src/lib/LibICloneableFactoryV4.sol +++ b/src/lib/LibICloneableFactoryV4.sol @@ -18,10 +18,7 @@ error ZeroImplementationCodeSize(); /// delegated account. error DelegatedImplementation(); -/// Thrown when the clone address already has code. On the open-salt path the -/// occupant is the exact clone asked for; on the namespaced path it is the -/// clone the same deployer deployed at that salt, with whatever `data` that -/// call passed. +/// Thrown when the clone address already has code. /// @param clone The occupied address. error CloneAddressOccupied(address clone);