Skip to content

GFQL implementation shrink: IR metadata and verifier helper residue #1567

Description

@lmeyerov

Goal

Shrink existing GFQL IR/metadata/verifier implementation code without changing behavior or colliding with the typed-schema PR.

Target 300-600 LOC of production GFQL implementation deletion/DRY if safely available. Tests/fixtures/changelog do not count toward the headline target; report them separately.

Context

Refs:

Planner/IR cleanup removed some private scaffolding under #1542. This lane should audit the remaining existing IR/metadata/verifier implementation for duplication and stale private helpers, while avoiding public typed-schema work and avoiding conflicts with #1457.

Candidate Surface

Start from latest master and audit this ownership area:

  • graphistry/compute/gfql/ir/*.py
  • graphistry/compute/gfql/ir/metadata.py
  • graphistry/compute/gfql/ir/verifier.py
  • graphistry/compute/gfql/ir/types.py
  • IR tests only as validation/support

Avoid changing public schema API files or behavior being introduced by #1457. If #1457 conflicts, stop and report rather than absorbing typed-schema feature work.

Required Protocol

  1. Build an inventory before editing: production symbol/file, callers, coverage signal, and expected implementation LOC deletion.
  2. Prioritize production GFQL implementation shrink. Test/comment deletion is secondary and must be reported separately.
  3. If implementation deletion opportunity is <300 LOC after a full audit, stop with an audit receipt rather than shipping a mostly-test cleanup PR.
  4. Preserve current IR behavior and public APIs.
  5. Use GFQL cleanup: add CPU/GPU coverage audit for dead-code candidates #1517 coverage as triage only; require static caller proof and focused validation.

Validation Expectations

  • Focused IR/metadata/verifier tests.
  • Planner/runtime tests if IR execution behavior is touched.
  • Broad non-cuDF GFQL selection if production paths are touched.
  • Ruff, typecheck, py_compile, surface guard if applicable, diff check.
  • Review protocol before marking ready.

Merge Policy

Open a PR when ready, but do not auto-merge. Coordinator must approve after reviewing production-code deletion, test/support delta, and validation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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