By: Tom Sydney Kerckhove <syd@cs-syd.eu>
Work out a component's lexicon once, and say what the store does The reachability walk ran per field, and a repository has a few thousand fields against a few dozen components, every site in one of which may draw on exactly the same types. It runs per component now. The comment over the dependency insert named insertKey where the call is repsert, which is the part that matters: a cabal file naming one dependency twice across a component's conditionals declares one edge, and an insert keyed on the edge would refuse the second. A dependency declared by one component of a package is not one its other components may use, and only reachablePackages' own spec said so. A resource says it too now, with a library and a test suite where only the test suite builds against the package holding the type: which component a site is in is what decides whether the type is within reach, and nothing before this would have noticed the extraction filing an edge under the wrong one.