Game.GoreAndAsh.Actor.Message

Documentation

class Typeable objectId => ActorMessage objectId where

The typeclass separates message API's of different type of actors

In general you don't want to have one global type to handle all possible types of messages, it will break modularity. Thats why you creates (with newtype) separate types of ids for each actor and statically binds message type (usually algebraic type) to the id.

The class implies that your id is some integer type, but it could be not. Just provide way to stable convertion of you id to integer and vice-versa.

Minimal complete definition

fromCounter, toCounter

Associated Types

type ActorMessageType objectId :: *

Binded message type, mailbox with id type of objectId would accept only this message type

Methods

fromCounter :: Int -> objectId

Convertion from global counter. Don't use it in client code as it could break type safety.

toCounter :: objectId -> Int

Convertion to global counter. Don't use it in client code as it could break type safety.

actorFingerprint :: forall proxy a. ActorMessage a => proxy a -> HashableTypeRep

Returns hashable fingerprint of actor that is stable across applications (unique by type name)