ratchetfreak

Another optimization that's possible (and encouraged) is allocating one big buffer for vertex and index data and suballocating from that for the per-frame data (round-robin style). For the pool you...

it's not going to be 100% exact though as rounding errors will accumulate and lose you up to log2(steps) = ceil(log2(54)) = 7 bits.

> Ok, but how does a given region of the linear buffer being mapped onto affect that? From the wasm code's point of view, it's still just a regular lookup...

The best option so far would be the fancy pointers in C++ allocators (which was supposed to be to support near/far) `wasm::ptr` however you will need to create specific specializations...

top level domains are much more flexible these days, you may be able to acquire .vk by itself.

I mentioned this in #435 but I'll repeat it here for prosperity Providing a row stride with the buffer would then be very nice addition for the APIs that require...

Has there been any consideration for the API for these decoders. Audio should be pretty simple, a config for communicating the sample rate, amount of channels, and bit depth. And...

It's hypothetical at this stage. and yeah that does complicate matters

A very much nice to have feature is a graph visualization of your objects memory. So you can get a easy overview of your state even when it's spread across...

A true hack would be to use a second imgui context just for the keyboard... It's output then gets sent to the primary context that hold the textbox.