-
Notifications
You must be signed in to change notification settings - Fork 344
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
Refactor to use C++ implementation of requirement gathering for Python. #3538
Conversation
The generated output of |
d220ed6
to
f8e3ebd
Compare
d4c389e
to
3895bf9
Compare
For now I've reverted back to using an Array, let's get this merged in and we can use a HashSet later if we agree on merging #3550. |
Wasn't following too closely but it seems like you do have agreement on merging that 🤔 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good to me, but I have one nit I'd like addressed.
Potentially yes, but no approval on the PR as of yet. |
34a1e08
to
1bf6779
Compare
1bf6779
to
5588d13
Compare
The current state of things is that the logic for gathering package requirements is duplicated in TS and C++. This PR moves it into workerd so that the same implementation can be used in workerd and EW.