haskus-system

It used to be one function per syscall: https://github.com/haskus/haskus-system/blob/ee3e0a69a263aaf... I did this to remove the boilerplate code, to make it easier to select the method (foreign primops or safe FFI foreign calls) and to make the conversion from the kernel tables simpler. However I may have to switch to a Template Haskell solution because the type-level approach with type classes and type families has increased the compilation time and forces me to use `-freduction-depth=0`.

Interesting, I was thinking about something like this, at least for exposing the raw Linux syscalls. I'm really happy this exists. Although I still have no clue what it's useful for, beyond my vague plans to speed up base file I/O and re-implement the RTS in Haskell, which never seemed that important so I never got around to... I've read https://github.com/haskus/haskus-system/blob/27bc422fccff455... and it still seems pretty weird to store the syscalls at type-level instead of defining them function-by-function. You don't have to define functions one-by-one, just use Template Haskell to generate them... and Syscall.read is much clearer than syscall @"read".