HN

Need help?
<- Back
C-events, yet another event loop, simpler, smaller, faster, safer

C-events, yet another event loop, simpler, smaller, faster, safer

thetechstech

Comments (11)

  • cryptonector
    Nice! I could use this :) (for open source work).Though I would prefer to have something not based on callbacks.
  • kevin_thibedeau
    void *rwtask(param_t v) { ... a = v->int_ptr; ... free(a); It seems architecturally unwise to have a callback responsible for freeing its parameters. At the very least this fossilizes dependency on the stdlib heap.
  • emersion
    My go-to small event loop library is https://github.com/any1/aml
  • miguel_martin
    See also: Nim's std/selectors API - https://nim-lang.org/docs/selectors.html, it supports: "Supported features: files, sockets, pipes, timers, processes, signals and user events." - here's a HTTP server event loop using it: https://github.com/guzba/mummy/blob/master/src/mummy.nim#L11...
  • mgaunard
    Why not io_uring? That's the biggest game changer.I guess because it's not possible to abstract away as much.