Custom-page-size and/or shrink memory #4006
Description
The custom-page-size feature is a standard proposal that overlaps with the current shrink_memory implementation based on heap_base in wasm_loader.
The unresolved question is whether we should retain both features or just maintain one
Given that shrinking memory is not a standard operation, yet there is consistently a need to reduce memory usage, should we make it controllable and/or configurable? For instance, by using a compilation option and/or a command line option.