From 32f5044eaf46e11b3b13c35644c7ad3cd1250c31 Mon Sep 17 00:00:00 2001 From: Robert O'Callahan Date: Wed, 4 Mar 2026 02:18:48 +0000 Subject: [PATCH] Clarify "Not passing module as function argument" comment This correct in terms of intent, it's just not fully enforced due to const laundering. --- passes/opt/opt_clean/wires.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/passes/opt/opt_clean/wires.cc b/passes/opt/opt_clean/wires.cc index d7ca215c4..28c792936 100644 --- a/passes/opt/opt_clean/wires.cc +++ b/passes/opt/opt_clean/wires.cc @@ -537,7 +537,7 @@ bool rmunused_module_signals(RTLIL::Module *module, ParallelDispatchThreadPool:: { // Passing actx to function == function does parallel work // Not passing module as function argument == function does not modify module - // TODO the above sentence is false due to constness laundering in wire_at / cell_at + // The above sentence signals intent; it's not enforced due to constness laundering in wire_at / cell_at AnalysisContext actx(module, subpool); SigConnKinds conn_kinds(clean_ctx.flags.purge, actx, clean_ctx);