Skip to content

[codex] rename graph API terminology#4

Merged
shinaoka merged 1 commit into
mainfrom
codex/general-graph-terminology
Jun 1, 2026
Merged

[codex] rename graph API terminology#4
shinaoka merged 1 commit into
mainfrom
codex/general-graph-terminology

Conversation

@shinaoka
Copy link
Copy Markdown
Member

@shinaoka shinaoka commented Jun 1, 2026

Summary

Breaking terminology migration for the public graph API:

  • Rename Fragment/FragmentBuilder to Graph/GraphBuilder.
  • Rename value and operation identifiers/keys/references to Value* and Operation* names.
  • Rename GraphOp/EvalGraphOp to GraphOperation/EvaluableGraphOperation.
  • Replace OpMode::Primal/OpMode::Linear with OperationRole::Primary/OperationRole::Linearized.
  • Remove OpEmitter from the public API; callers use GraphBuilder::add_operation or higher-level downstream builder traits.
  • Rename public fields from op/mode to operation/role, and materialized graph fields from vals/ops to values/operations.
  • Update README wording and public doctests to use the new names.

Why

Fragment and Emitter were implementation-oriented terms that leaked older terminology into downstream APIs. The new names use general graph vocabulary and align with tidu/tenferro public terminology.

Validation

  • cargo test --release
  • cargo test --doc --release
  • cargo clippy --all-targets --release -- -D warnings
  • cargo fmt --all --check
  • git diff --check

Notes

This is intentionally breaking; no compatibility aliases are included.

@shinaoka shinaoka merged commit 691def2 into main Jun 1, 2026
3 checks passed
@shinaoka shinaoka deleted the codex/general-graph-terminology branch June 1, 2026 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant