pub fn listings() -> DepSceneExpand description
The six listings the core’s unit test env::listing_tests makes in
every order, each load’s number its index: x, y, X, x, y and
x, the last as a dependency. Each file is a SerializedFile holding
one named object whose path id is its load’s number + 1, so a listing’s
file and object tell its load. A key is listed again by a later load and
by an earlier one, after it moved, two keys lower to one name, and the
last x is a dependency’s, which objects skips. Not a scene of
super::scenes: tools/fixtures/env_race.py records UnityPy’s
env.files after every set of these loads, made in the order of their
numbers (review round 16’s follow-up: the test’s expected values were a
hand-written model of a Python dict).