8:49:37lokeDo you feel this branch is ready to merge?
8:50:47jackdanielno for three reasons: 1. it needs to be remade to have clean commit history (right now I've just slapped a few commits on top to show what I have in mind), 2. I'm still thinking about synchronous api, 3. documentation is incomplete
8:51:28jackdanielalso, nomen omen, nobody has reviewed my code so far and I'm sure I've planted numerous issues in there
9:22:45beachOh, sorry, it won't show the latest annotations.
9:23:03beachACTION should learn to read the context before blabbing.
9:27:02jackdanielbeach: maybe you will be interested in this non-unix operating system comparison to unix: https://bzdww.com/article/163937/ (fuchsia os)
9:28:02jackdanielof course there is a lot of FUD in there, but some interesting insights and ideas too
10:06:28lokeYeah, so removing it should be nothing more than a formality.
10:06:56jackdanielthere is some return value mangling and process-next-event calls distribute-event on a result event, but yes, get-next-event is just a clutter
18:18:13jackdanielbased on a name and prototype, what would you expect this function to do? (it doesn't exist) -- (defgeneric event-listen-or-wait (sheet &key timeout wait-function))