Skip to content

Finalise new outcome API - #1100

Merged
tturocy merged 1 commit into
masterfrom
dev_outcome
Aug 30, 2026
Merged

Finalise new outcome API#1100
tturocy merged 1 commit into
masterfrom
dev_outcome

Conversation

@tturocy

@tturocy tturocy commented Aug 30, 2026

Copy link
Copy Markdown
Member

This completes the work initiated with the introduction of make_outcome:

  • Game.add_outcome, Game.delete_outcome, and Game.set_outcome are removed from pygambit, along with the underlying C++ GameRep::NewOutcome, GameRep::DeleteOutcome, GameRep::SetOutcome, and PureStrategyProfileRep::SetOutcome.
  • MakeOutcomeNull and make_outcome_null are introduced to allow for "un-setting" an outcome
  • Calling code no longer needs to do bookkeeping on outcomes. Instead, the game object manages the invariant that all outcomes are referred to at least once in the game.

This completes the work initiated with the introduction of `make_outcome`:
* `Game.add_outcome`, `Game.delete_outcome`, and `Game.set_outcome` are
  removed from pygambit, along with the underlying C++ `GameRep::NewOutcome`,
  `GameRep::DeleteOutcome`, `GameRep::SetOutcome`, and
  `PureStrategyProfileRep::SetOutcome`.
* `MakeOutcomeNull` and `make_outcome_null` are introduced to allow for "un-setting" an outcome
* Calling code no longer needs to do bookkeeping on outcomes.  Instead, the game object manages the invariant that all outcomes are referred to at least once in the game.
@review-notebook-app

Copy link
Copy Markdown

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@tturocy
tturocy merged commit bd1c448 into master Aug 30, 2026
26 checks passed
@tturocy
tturocy deleted the dev_outcome branch August 30, 2026 13:20
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