Parallelism

Open
#37 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
performance, tooling

Research direction

No files or tests are named. Start by tracing how resyntax macroexpands and analyzes independent modules, then investigate how worker places could schedule that work safely. Done means large-codebase analysis runs in parallel while preserving the existing analysis results.

Written by the indexing model from the issue text.

Description

adoption barrier enhancement

Running resyntax on large codebases is slow, since it needs to macroexpand everything. But analysis of different modules is independent so it should be easy to parallelize the work using worker places.

Dominant language
Racket
Stars
70
Forks
11
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jackfirth/resyntax

All issues in jackfirth/resyntax

Similar issues

More Performance issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.