Marshall Polaris

I plan on building and binding this code. Is upstream interested in a patch to do so by default? Or, if not, would it be good to add an option...

Hmm. I could implement it as a separate build pipeline that produces a separate WASM blob, but it refers to a fair chunk of Bullet code, so that would result...

Oh yeah, and also creating the closure in `getLongestEdgeIndex` shows up. That one's easy to fix.

Another idea: right now the split strategy code returns a temporary object with the split parameters (axis and coordinate.) Instead, the split strategy code could populate the new bounding box...

Everything I wrote in here is now fixed up except for the very last comment. By the way, it looks like on the example page nowadays, one GC almost always...

You're definitely right that currently the code assumes that every user will have a publisher which is sort of the "master" connection for that user, or else things don't make...

(In general, once multistream is in, I'm open to doing a bunch of work to refit the plugin to your needs and to anyone else's needs who is interested in...

It looks like you are probably getting a somewhat old version of Rust -- [`MaybeUninit` was introduced in 1.36](https://doc.rust-lang.org/stable/std/mem/union.MaybeUninit.html). [Debian stable has Rust 1.41](https://packages.debian.org/stable/rust/rustc), so it should be working. Sorry...

It looks like specifying a minimum Rust compiler version is [coming soon](https://github.com/rust-lang/rust/issues/65262).

Makes sense. I'm 90% sure that the only reason we used to use H.264 over VP8 was for Mobile Safari support. If and when iOS supports something more modern with...