Wrong primitive names in LLVM I/O about effekt HOT 2 CLOSED

It's writeFile, isn't it? Since we don't write files in the test, dead code elimination removes it before it causes problems

from effekt.

I'm quite alarmed that the test in stdlib/io/files/async_file_io.effekt didn't catch this 🤔
https://github.com/effekt-lang/effekt/blob/cd741e8a4576c62ab318efd48fc0831958ba7e8d/examples/stdlib/io/files/async_file_io.effekt

EDIT: I tried running the LLVM stdlib tests and it appears that the test in question passes:

effekt.StdlibLLVMTests:
  + examples/stdlib/bytes/bytes.effekt (llvm) 2.928s
  + examples/stdlib/io/promise.effekt (llvm) 1.146s
  + examples/stdlib/io/files/async_file_io.effekt (llvm) 1.416s

The test works when ran directly:

$ effekt --backend=llvm examples/stdlib/io/files/async_file_io.effekt
Running program
Done
Some contents

{ msg: "Hello World!" }

done reading files.

but I don't understand why 😔
Well, the test only uses the readFile function and not the readFile operation which is then handled with filesystem. If I had to guess, the renaming is OK in one of them and not in the other...

from effekt.