enum architecture in client
#1
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: atiran/txtris#1
Loading…
Reference in a new issue
No description provided.
Delete branch "enumpattern"
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?
So, I restructured the app into separate sections for each menu using enum match statements, so that each game state (i.e. main menu, 40l, login, exit) is separated and easier to reason about. It also makes the code more "Functional programming" style, which I believe removes a lot of headaches with references and such (that's personal perspective). I made it a pull request since its such a big change, and idk if you want to keep it like this (although I'd recommend it)
WIP: Enum Architecture in txclientto Enum Architecture in txclientEnum Architecture in txclientto refdactor: enum architecture intxclient
refdactor: enum architecture into refdactor: enum architecture intxclient
client
refdactor: enum architecture into refactor: enum architecture inclient
client
refactor: enum architecture into enum architecture inclient
client