Show HN: A dead code killer for Erlang

#1

Post by elbrujohalcon » Thu, Jan 21, 2021, 10:21 AM UTC

Show HN: A dead code killer for Erlang
tech.nextroll.com

Re: Show HN: A dead code killer for Erlang

#2

Post by inter_netuser » Thu, Jan 21, 2021, 11:25 PM UTC

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

Re: Show HN: A dead code killer for Erlang

#3

Post by wiml » Thu, Jan 21, 2021, 11:42 PM UTC

inter_netuser wrote: post #2

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

I don't think you're forced to act on anything that it finds; it just points you at things that might be removable cruft.

Re: Show HN: A dead code killer for Erlang

#4

Post by dnautics » Fri, Jan 22, 2021, 1:42 AM UTC

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.

I imagine this tool also has a hard time identifying function invocations via erlang:apply

Re: Show HN: A dead code killer for Erlang

#5

Post by fouc » Fri, Jan 22, 2021, 2:08 AM UTC

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