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
We need to have a good way to test the library once everything is up and running. It is easy to introduce segfaults or other problems (such as hangs) due to the use of sockets. There is a lot of untyped code which has to align with each other.
I wonder if a library like lsp-test would be good inspiration for how to perform the necessary testing.
This question is moot anyway until there is a GHC release which has the necessary RTS methods in to support the interface.
The text was updated successfully, but these errors were encountered:
We need to have a good way to test the library once everything is up and running. It is easy to introduce segfaults or other problems (such as hangs) due to the use of sockets. There is a lot of untyped code which has to align with each other.
I wonder if a library like lsp-test would be good inspiration for how to perform the necessary testing.
This question is moot anyway until there is a GHC release which has the necessary RTS methods in to support the interface.
The text was updated successfully, but these errors were encountered: