ˌbodʲɪˈɡrʲim

I'd rather refrain from architectural changes without @UnkindPartition's explicit consent. It was a conscious choice, and I believe the intention was to evolve API separately (see #262 and comments about...

I have concerns about re-exports from other packages, but AFK, will be back next week.

My concern is that a specific version of a package should provide a stable API, whatever build plan. This means that for re-exported functions each version of the proposed `tasty-hunit`...

> I thought it's only the case when the instances are orphans, and in that case it would be a major bump anyway? No. Imagine re-exporting `HUnitFailure` from `HUnit` in...

@martijnbastiaan sorry, I don't have bandwidth for this right now. Could you possibly summarise all breaking changes here (both API and behaviour)? CC @VictorCMiraldo @adamgundry @andreasabel as other maintainers.

> TreeFold.foldSingle takes an extra argument ExactPath. Can this breaking change be avoided by introducing a new fold and expressing existing foldSingle via it?

@martijnbastiaan could you please share what kind of dependency graph is typical for Clash test suite? Is it chains of depending tests?

I agree that the infrastructure for dependencies between tests is wanting, but I feel that your approach covers only a fraction of cases, but required changes are quite profound. My...

Correct, none of my examples needs a DAG. However, the shape of `TestTree` is not necessarily in correspondence with a dependency tree.

@martijnbastiaan to be very clear, I agree that the dependency design is inconvenient and I also agree that if we were doing it from the scratch and with our current...