Skip to content

Library loading refactor, drop analysis error checking #1845

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

Merged
merged 9 commits into from
Nov 21, 2018

Conversation

jcollins-g
Copy link
Contributor

Analysis error checking is too difficult to do at this stage, so just drop it. It was inaccurate before.

Cleans up how we calculate libraries to be sure we get the transitive set of libraryElements when landing, and eliminate duplicitous excludes checking.

@googlebot googlebot added the cla: yes Google CLA check succeeded. label Nov 20, 2018
@jcollins-g
Copy link
Contributor Author

PTAL. I've changed how we're getting LibraryElements to a method that is not as horribly slow, and also eliminated some other inefficiencies to gain back some performance lost with this change.

@@ -6640,14 +6605,16 @@ class PackageBuilder {
}
}

int counter = 0;
int counter2 = 0;
Copy link
Member

Choose a reason for hiding this comment

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

I don't see any reference to these fields. Are they needed?

If so, consider renaming them to indicate what they're counting.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

whoops, these are debugging leftovers. Fixed.

@jcollins-g jcollins-g merged commit 009daa9 into master Nov 21, 2018
@jcollins-g jcollins-g deleted the library-loading branch November 27, 2018 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Google CLA check succeeded.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants