Skip to content

[Refactor]: Remove stale dead_code allowances in privacy module #28

@AashishH15

Description

@AashishH15

Problem

privacy.rs has broad dead-code allowances that may be stale now that privacy helpers are used by the assembler.

Evidence

  • privacy.rs (line 1) has #![allow(dead_code)], and line 47 (line 47) has another #[allow(dead_code)]. The privacy helpers are now used by the LLM assembler, so these suppressions look stale.

Scope & constraints

No response

Proposed approach

Remove global #![allow(dead_code)] and keep only targeted allowances if needed.

Acceptance criteria

  • No unnecessary allow-lints.
  • Compiler warnings reveal real dead code.

Test plan

cargo clippy / preflight.

Metadata

Metadata

Assignees

No one assigned

    Labels

    refactorImprove internal structure without changing behavior

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions