spring4175

@Erk- I have provided a cluster events alternative: ```rust use futures::StreamExt; use std::{collections::HashMap, env, future}; use twilight_gateway::{stream::{self, ShardEventStream}, Config, Intents}; let token = env::var("DISCORD_TOKEN")?; // callback to create a config...

Due to the new cluster alternative returning mutable references to shards, the list item on the checklist, "give user mutably referenced messages instead of owned", may not be possible. Providing...

> Now that `ShardEvent` is removed I've thought of the difference between `Event`, `GatewayEvent` and `DispatchEvent`. `Event` is now just a flattened `GatewayEvent`, which in turn is a `DispatchEvent` plus...

> why have the stream's `Item` be `(ShardRef, Message)` instead of `(ShardId, Message)`? these event/message stream implementations keep a list of unordered futures of all shards between ready polls of...

Assigning to self as this will likely be fixed as a result of my gateway refactor.

I'm unsure I understand this PR. Doesn't this remove support for parsing field errors? https://discord.com/developers/docs/reference#error-messages

> The message variant seems completely out of date. In what way is it out of date? If it is, shouldn't we get it up to date? These object and...

> I thought they were replaced/deprecated in API v8, other API error responses are also undocumented which makes it look unsupported to me. Quite the opposite, they were *introduced* in...

Triage: deferring updating + merging to likely 0.17

@vilgotf was this meant to be reopened?