Our error handling is rather underdeveloped. In particular, we have several instances where we simply call error which should really be some kind of "abort and return -1" statement (for the C ABI).
For socket handling (reading and writing, as in Graphics.Sudbury.Socket.Wayland), we need to deal with sockets that close. (oh and when looking at this, please also compare the size limits for reads and writes with libwayland)
Our error handling is rather underdeveloped. In particular, we have several instances where we simply call
errorwhich should really be some kind of "abort and return -1" statement (for the C ABI).For socket handling (reading and writing, as in
Graphics.Sudbury.Socket.Wayland), we need to deal with sockets that close. (oh and when looking at this, please also compare the size limits for reads and writes with libwayland)