`deps` command has poor memory footprint
Closed this issue · 0 comments
johanfylling commented
The deps command recursively visits each dependency of a given ref; collecting the ref for each hit. Duplicate refs are pruned after the fact, and rules already visited will be revisited as they are encountered. This results in a very poor memory footprint and execution time for highly "connected" Rego projects.