From the epic #278 deep review (code pass). mlx_impl/core.py:2618-2623 documents an ordering dependency between the adaptive-PDF switch hook and the share_comps merge hook and honestly notes "no test here pins the hooks' relative order... a future accidental swap would not be caught." Torch has the same relative ordering. Per the no-untracked-TODO norm, this issue is that tracking record: add a cross-backend test pinning the order (or an in-fit assertion), or document why the order is actually inconsequential.
From the epic #278 deep review (code pass). mlx_impl/core.py:2618-2623 documents an ordering dependency between the adaptive-PDF switch hook and the share_comps merge hook and honestly notes "no test here pins the hooks' relative order... a future accidental swap would not be caught." Torch has the same relative ordering. Per the no-untracked-TODO norm, this issue is that tracking record: add a cross-backend test pinning the order (or an in-fit assertion), or document why the order is actually inconsequential.