Saving the player's state can panic past the Result it returns #53
Labels
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rosa/casino#53
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Saving the player's state takes the parent of the path it was given without
checking there is one, and treats a failure to serialize as unreachable — both
inside a function that already returns a
Resultand has a caller ready tohandle one. Either can bring the process down at the point a player's progress
is being written, which is the worst moment for it.
This is the same defect as the one fixed in the config's own save, and the same
fix. It was left out of that work because state is not hard to test today — it
takes a path already — so fixing it there would have been a change riding along
rather than one serving the goal.
Blocked by