haskell-distributed / haskell-distributed/distributed-process
Threadscope integration
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
Not sure what this would look like but it was originally logged for -platform and I think if it has legs it's better suited here.
Presumably there's not much to do, as a process is implemented using forkIO already. Do we want to provide stats (such as issue #89 provides) there as well, or would it be better to expose them in some other bespoke tool?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #89's stats and the existing forkIO-based process implementation. Clarify whether Threadscope should expose those stats or use a bespoke tool; done requires an agreed integration scope, since no files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100