John-John Tedro

Sorry, the best I can do for now is recommend you try the [`nightly` release](https://github.com/udoprog/OxidizeBot/releases/tag/nightly). That's the one I run and it works for me. If that fixes your issue...

Thank you, so there seems like there could be some issue related to when a component (like the player) fails to initialize. That might be worth investigating!

This is a known (but undocumented) behavior. If something holds onto a waker it can cause sporadic wakeups in unrelated futures. The assumptions have been: * This should not cause...

Feel free to take a stab at it if it's something you're interested in doing. The previous comment was just for me to personally be able to prioritize, not to...

It would be a nice addition!

Hah, for sure! Maybe the import location should be specified explicitly or something like it.

Another feature I'd appreciate is to be able to somehow pass a mutable environment through to both closures since I somehow need to reference the virtual machine being used. This...

> I don't think supporting fallible hasher is worth adding this level of complexity to the API. In most cases this isn't needed, and you can always emulate it by...

> `hasher` absolutely cannot be allowed to fail, we rely on this when rehashing the table. See `rehash_in_place` where if the hasher panics then we drop all elements in the...

I couldn't produce a modification for a failing `eq`, but here is one which is avoided for a failing `hasher`: ```rust use hashbrown::raw::RawTable; fn main() { let mut table =...