Is your feature request related to a problem? Please describe.
rebar3 uses ignore_xref directive to silence xref analysis when an exported function is not used in the scope of the analysis.
It might so happen that after a while you start using the "ignored" function, but the directive remains in the code, which would potentially classify as "dead code".
Describe the solution you'd like
Should hank care about this, this being rebar3 but also the "standard" Erlang build tool (which would make ignore_xref part of the scope hank "knows/cares" about)?
Describe alternatives you've considered
Keep having unnecessary ignore_xref directives here and there and reviewing that code, if/when I remember.
Is your feature request related to a problem? Please describe.
rebar3usesignore_xrefdirective to silencexrefanalysis when an exported function is not used in the scope of the analysis. It might so happen that after a while you start using the "ignored" function, but the directive remains in the code, which would potentially classify as "dead code".Describe the solution you'd like
Should
hankcare about this, this beingrebar3but also the "standard" Erlang build tool (which would makeignore_xrefpart of the scopehank"knows/cares" about)?Describe alternatives you've considered
Keep having unnecessary
ignore_xrefdirectives here and there and reviewing that code, if/when I remember.Additional Context
None.