Skip to content

Figure out data 'visibility' problem in games #4

@cronburg

Description

@cronburg

Solutions:

  • Pass only visible things to a function that can only see certain things (i.e. parametrize it more explicitly) - this is the ad-hoc solution.
  • Pass the whole data structure, but wrap it in a visibility monad which only exposes certain accessors as defined by the visibility instance definition?

Other issue: you can sometimes see the fact that a list exists and e.g. the top card on a list, but not how many cards are in the list.

In games which transmit data / do IO, we really do need to censor the data defined to be invisible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions