feat/hunspell: check content origins in parallel #123
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR accomplish?
Makes
hunspell
iterate over content origins in parallel, which yields a huge speedup on machines with more than 2 cores.Ref #104 .
Changes proposed by this PR:
Introduce
rayon
to parallelize iteration execution.Notes to reviewer:
This does not yet use a
mpsc
to prepare individual suggestion sets per origin, but merges them into one still. So for large projects there is still a inactivity time noticable. This will be addressed in futures commits.📜 Checklist
./demo
sub directory