Erlang Module Export vs. Private Functions: Avoiding Accidental Public Access

Erlang Module Export vs. Private Functions: Avoiding Accidental Public Access

Goal: Keep helper predicates hidden while still enabling quick prototyping with the -export_all compiler flag.

Constraints

• Erlang has no explicit private attribute; non‑exported functions rely on convention.
• The -export_all option overrides any explicit export list, making accidental exposure likely.

Unresolved Decision

Whether the language should introduce a formal private attribute or similar mechanism to prevent accidental export and aid static analysis.

Open Questions

1. Does the current compiler warn when a function appears in an export list but is not defined?
2. What would be the backward compatibility impact of adding a private attribute to existing modules?
3. Can tooling be extended to detect unintended exports when -export_all is used?