You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 3, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 3, 2024. It is now read-only.
Hello, currently this package in not actively maintained by it's primary maintainer. I'll try to take a look into this issue but I can't guarantee that I'll do that promptly.
Major bugs will be fixed but may be not very promptly. All PRs will be reviewed and merged possibly with delays. Versions bounds will be updated upon a notice. Unless somebody will volunteer to drive this package forward you should not expect much improvements. I'm not sure that I can say that I totally trust codebase so possibly there is a room for improvement , but as far as I know there are some users of this package and it works for them.
I think such situation will stay at least in the middle term.
What I've written is only about distributed process platform packages like extras, client-sever. Network transport family, distributed-process itself and d-p-asynx are properly maintained.
In our practice we primarily use distributed-process, network-transport-tcp, network-transport-inmemory, distributed-process-async, and build our primitives on top. There are also distributed-process-platform with a number of packages inside that try to mimic Erlang's OTR, they are not critical for writing code.
Sorry, I'm trying to get back to maintaining these packages but have not had access to a working environment for quite some time now. Hopefully will be back on board soon but efforts to get back to the project stalled last year.
I may be doing something wrong, but I'm having trouble getting this to build with GHC 8.