Josh Goebel

Well sure - if you have to hard-code the heap size then we'd want to hard code it to take advantage of all the free RAM we have... but I'd...

> Of course, the WASM memory layout could be changed to avoid storing data at 0x00000, but that would be a major change and break binary compatibility, so probably not...

That would require a LOT of special cases - the memmap is like hard coded into so much of the codebase. It's a literal chunk of 96kb in RAM in...

19kb out of 256kb isn't TERRIBLE if it's a one time cost...

> but since the code is stored in the BINARY chunk, isn't the limit actually 64k? When needed it's distributed across multiple chunks... so for a large cartridge where would...

> The size penalty isn't just a one time cost, but it's also not too bad as far as I can tell. Well I meant is it MOSTLY the 15kb...

You shouldn't need to link to it at all if Rust provides it itself - unless somehow the fact of us exporting the function itself is causing issues... there is...

Performance, consistency, etc. Whatever language someone is in they should be able to count on the TIC-80 built-in API. > but the TIC-80 versions appear to be limited to the...

> Am I permitted to write my own version of the calls in Go, defaulting to the native API only when necessary? How would that help the situation? I think...

> but it would be nice to have that documented in the README. PR welcome. > Probably just need to update the demo to use the wrappers instead. I think...