This issue exists to discuss the binary encoding of custom page sizes.

Relevant Previous Discussion

@fitzgen said

We could also encode the page size as n in 2^n which I think would save some LEB encoding bytes.

@alexcrichton said

Not relevant to this PR, but for the future PR to fill this in I found this table in the memory64 proposal perhaps a good starting point for determining a binary encoding. (aka pick the next bit in the prefix byte and have it represent a "trailing log2 page size i32" and that may be all that's necessary)