Lazy Guild memory usage
Lazy guilds use murmurhash3 for their
id field. We were not expecting this while implementing it. It is a punch on the already thorough implementation.
GuildMemberList instances are separated per guild and per channel, this means two channels with the same set of overrides will get two separate instances of the list. That can cause memory problems as you will have the same data spread out memory.
LazyGuildManagerwork with those kinds of IDs internally, instead of channel IDs (maybe the requests can be in channel IDs, which doesn't break internal APIs)