Folkert de Vries

fun thing: I ran `zig translate-c host.c > host.zig` and then everything works fine. Only difference between the host binaries seems that the C host executable has two `RELRO` program...

This passes CI now. Turns out fixing the valgrind issues was enough. There were two silly bugs, and the host did not free a roc string. How should we proceed?...

I'm not sure we can. When that stack becomes much bigger, the C compiler reports overflows

numeric overflows in arithmetic using that stack size

to replace current `Set`, we will need `union` and `difference`. These are used in our examples (e.g. `AStar`)

How do you run the tests? does `cargo test-gen-llvm` still run all the llvm tests (idem for -dev and -wasm)?

CI fails in a weird way. I'll re-run and see if it's a flake or real ``` ---- cli_run::helloWorld stdout ---- thread 'cli_run::helloWorld' panicked at '`valgrind` exited with no exit...

we have a test that checks that all examples are part of a cli_run test (to prevent the examples going stale). Could you add such a test?

@bhansconnect the test/program fails when using the surgical linker. Not sure if that is easy to fix or if we should find a workaround for now

This is interesting. The `f` function has a function type, and does not capture anything. So yeah, `f`is not in the set. The code we want to generate here is...