Expand description
The rendered shard view, and the private overlays layered on top of it.
A ShardView holds each fact once, whoever ends up seeing it. That is
the whole reason the model is linear: W counts facts, while materializing
one view per connection would count copies.
An Overlay holds the elements visible to exactly one connection. It is
never journalled and never merged into the shared view: an element is shared
xor private (guide 3.4), and crate::build enforces that.
Structs§
- Action
- One action a flavor offers to one connection.
- Channel
- A channel in the shared view.
- On
- Where a context action is offered in the client’s interface.
- Overlay
- Elements visible to exactly one connection.
- Shard
View - Everything one shard renders, each fact held once.
- User
- A user in the shared view, or in one connection’s overlay.
- User
Flags - The boolean user state Mumble carries on
UserState.
Type Aliases§
- Actions
- The actions offered to one connection.