4 ms·
> You call it Merkle-style tree despite the fact it is obviously a DAG? All trees are DAGs so that's not really adding much.
by fnord123 4y ago
> You call it Merkle-style tree despite the fact it is obviously a DAG?
All trees are DAGs so that's not really adding much.
- progbits 4y agoBut not all DAGs are trees and the one in the picture (and generally all graphs of dependencies) isn't.
- nl 4y agoIt's a multirooted tree. And describing it as a Merkle-style tree conveys additional implementation about the implementation - presumably the tree stores the hash ("computed from all of its source files and inputs") which just saying "it's a DAG" doesn't tell you.
- dymk 4y agoCalling it a Merkle style DAG would have solved the issue. Or just avoid the fancy names and call it what it is: they walk the dependency graph to identify build targets that have a changed dependency.