Module orchestrator::memory

This module keeps track of al the Memory related abstraction Memory is considered the layer that keeps track of the exercise, submission, user… It’s not important how it is implemented, or how the data are structured. It has to respond to some simple queries in the Memory trait.

The Memory trait is actualy formed by two traits: StatelessMemory and StateMemory. This is needed to expose StateMemory only when it is actualy possible to specify the state.

Structs

• Admin
  Admin variant, used as a type-state-machine
• Authenticated
  Authenticated variant, used as a type-state-machine
• Unauthenticated
  Unauthenticated variant, used as a type-state-machine
• User
  An user, the variant S represent the type of user (if it is Authenticated, Admin, or Unauthenticated).

Traits

• Memory
  auto trait that rapresent the union of stateless and state Memory
• StateMemory
  This is the trait that contains all method of the memory that does require knowing the state. Is not always available
• StatelessMemory
  This is the trait that contains all method of the memory that does not require knowing the state
• UserState
  A valid UserVariant

Attribute Macros

• async_trait