See how hard it would be to make Table's seats field be a new type, Seat that contains its own action and player fields.
Currently action and this_round_action are both fields inside Player. Pots are built by summing all the action from the various players. That means we can't move a player who has folded until after the hand is over. That would make table splitting (#1088) even more painful. So, see how hard it would be to refactor in a Seat struct that holds action, this_round_action and player (which is an Option<Player>).
Turns out, I did this spike before creating this issue, so although it took a couple days, it's done.
ctm
commented
1 year ago
See how hard it would be to make
Table'sseatsfield be a new type,Seatthat contains its ownactionandplayerfields.Currently
actionandthis_round_actionare both fields insidePlayer. Pots are built by summing all the action from the various players. That means we can't move a player who has folded until after the hand is over. That would make table splitting (#1088) even more painful. So, see how hard it would be to refactor in aSeatstruct that holdsaction,this_round_actionandplayer(which is anOption<Player>).Turns out, I did this spike before creating this issue, so although it took a couple days, it's done.
Whee!