Show HN: A dead code killer for Erlang

> Hank will detect and warn you about valid parts of your code that could potentially be deleted or at least refactored based on rules.

The place I work runs a heterogeneous erlang cluster (cluster-as-service-mesh), I assume the best way to deal with this is to mark off that module, or the specific cluster exports, to be ignored.<p>I imagine this tool also has a hard time identifying function invocations via erlang:apply

How do you handle code that you want to keep in place commented out, because it might be needed later for debugging&#x2F;etc?