Skip to main content

Module tree

Module tree 

Source
Expand description

Every file of every release, merged into one tree, with the numbers that come out of doing it.

The per file work is in merge.rs. What is here is the part that makes it a tree: the union of the paths, the order they are done in, the writing, and the count of what happened. The count is the point as much as the tree is, because spec/cross-compile/08-sysroots.md section 8.3 names 210 files that change somewhere between 2.28 and 2.44 and this is what turns that survey into a statement about an artifact: how many files needed a conditional, how many could not be cut finer than the whole file, and what the tree weighs against the installs it came from.

Structs§

Input
One installed header tree and the release it is.
Record
What one file became.
Report
What a merge of a whole tree did.

Functions§

merge_trees
Merges every input tree into one at out.