Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make UAST check parallel #448

Closed
wants to merge 1 commit into from
Closed

Make UAST check parallel #448

wants to merge 1 commit into from

Conversation

m09
Copy link
Contributor

@m09 m09 commented Dec 12, 2018

Fixes #394.

@m09 m09 added this to the 0.1.0 milestone Dec 12, 2018
Signed-off-by: Hugo Mougard <[email protected]>
Copy link
Collaborator

@vmarkovtsev vmarkovtsev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the implementation and also taking into account that the speedup is not dramatic, I think that it's better to solve this properly after the release. We should allow BblfshClient to be constructed on top of a stub and a channel.
Thus we remove the type ambiguity in _check_vnode. It will also simplify code in other places: we are not supposed to work with low-level stubs directly. We should also add BblfshClient.close() which I suggested Waren a few days ago.
Our DataService.get_bblfsh() would return a BblfshClient inheritor which does the necessary bookkeeping in it's overloaded close().

This requires PR-ing to bblfsh/client-python and can take a few days.

@m09
Copy link
Contributor Author

m09 commented Dec 12, 2018

👍

@m09 m09 closed this Dec 12, 2018
@m09 m09 deleted the feature/parallel-uast-check branch December 13, 2018 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants