Sophie Wallace

Trying to collate all that... - [x] call_ext (pending https://github.com/SpaceManiac/SpacemanDMM/pull/353) - [x] pointers (`&` syntax, is there more than that? do we need static typing support for it?) - [...

example?

also should unhook any already-hooked methods (or they might run without strings being interned etc.

The issues with this in extools were: - memory usage, it can't stay in ram (at least in the byond address space) - detecting deleted lists/datums. The code extools hooked...

possibly fixed by byond 514.1585?

I don't see any map icon code in this PR

No need for separate targets. The binaries can be stripped post-build with the `strip` command line utility. I'm not sure this really needs to be done on this repo since...

It's a little bit of a "standard" to have `x.so` and `x.so.dbg` available and to use the debug version when necessary for debugging core dumps. Both are valid binaries (but...

```toml [target.i686-pc-windows-msvc] rustflags = ["-C", "target-feature=+crt-static"] ``` :)

That's because they're used by Chromium. It'd probably be sensible to call in to the base Lua functions though.