forked from pantsbuild/pants
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Upgrade to a recent version of zinc. - Support version 5 of the analysis serialization format. - This version moves the CompileSetup sections from the end of the file to the beginning. - This version adds a "name hashing" section to the CompileSetup. - Add a pants option to turn name-hashing on. - Fixed the implementation of is_nonempty_analysis(), which can no longer simply look at a prefix (because the order of elements in the zinc analysis file has now changed). We had already added support for splitting/merging the analysis sections used by name hashing, under the assumption that their structure and semantics were the same as for their equivalent pre-name-hashing sections. We had been told by TypeSafe that this assumption was correct, but had never tested it. I have now verified that it is indeed true. Note that when name hashing is turned on, the member* and inheritance* sections are populated by zinc INSTEAD OF the direct* and public* sections. However the "used names" section is populated AS WELL AS the "class names" section. This means that turning on name hashing will cause analysis files to be larger. Whether this is significant, in particular wrt split/merge times, needs to be measured. I suspect it should be OK, since split/merge of these sections is simple - they don't have the complicated internalization/externalization logic. Testing Done: CI passes: https://travis-ci.org/pantsbuild/pants/builds/50907336 Reviewed at https://rbcommons.com/s/twitter/r/1779/
- Loading branch information
Benjy
committed
Feb 25, 2015
1 parent
1da125c
commit 2d9972a
Showing
11 changed files
with
109 additions
and
141 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.