dart-lang
Add a lint to ensure library dependency graph is a DAG
I like this type of rule but I think it needs a more comprehensive specification, there are objects that know about each other and that is OK, for instance similar static analysis programs in java and c# allow it at the package or namespace level, How should we do it here? The equivalent might be directory, but so far I haven't seen that convention followed in the dart community.
Even in that case. I notice a strong tendency for one file per library and one class per file.
While this is the kind of thing I would like to have contributed from day one, it might beyond the scope of a linter, and at the very least will face challenges to be as performant as needed for a linter.
Wasn't there some discussion about tagging linter rules in slow and fast and then for example run fast rules live and others only on commit or similar?
