Skip to content

ecosystem-integration: migrate to ternary_types::Ternary#2

Open
SuperInstance wants to merge 4 commits into
masterfrom
ecosystem-integration/ternary-types-migration
Open

ecosystem-integration: migrate to ternary_types::Ternary#2
SuperInstance wants to merge 4 commits into
masterfrom
ecosystem-integration/ternary-types-migration

Conversation

@SuperInstance
Copy link
Copy Markdown
Owner

Summary

Replaces the crate's own enum Ternary with a re-export of the canonical ternary_types::Ternary.

Changes

  • Add ternary-types as a dependency
  • Replace custom enum Ternary with pub use ternary_types::Ternary
  • Add TernaryExt trait for any crate-specific methods that were on the original enum
  • Update all variant name usages to the canonical names
  • Version bump to 0.2.0
  • Add migration badge to README

Variant Name Mapping

Old New
Ternary::Neg Ternary::Negative
Ternary::Zero Ternary::Neutral
Ternary::Pos Ternary::Positive

See the ecosystem integration PR for context.

SuperInstance and others added 4 commits June 5, 2026 09:12
…_AND_PLAY, CONTRIBUTING)

Follows DOC_STANDARD.md conventions:
- 5-tier doc system: README + 4 supporting docs
- Ternary {-1, 0, +1} mapping with domain-specific semantics
- Cross-repo references to sibling ternary crates
- Zero is not nothing: neutral state is meaningful

Part of fleet-wide documentation initiative.
- Add ternary-types dependency
- Replace custom enum Ternary (Neg/Zero/Pos) with pub use
- Add TernaryExt trait for to_f64() method
- Version bump to 0.2.0
- Add migration badge to README
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