David Seddon

I've made a start on documenting an API in Grimp [here](https://github.com/seddonym/grimp/pull/253).

> The whole idea about presenting cycle breakers is at least one level cooler than presenting raw cycles. I will continue a review of the idea in Grimp PR. Great!...

> I wonder how nominate_cycle_breakers should be utilized in the acyclic contract implementation. This is what I meant by the depth argument. It would default to drilling down to all...

I am going to concentrate on implementing `find_cycle_breakers` within Grimp, so if you want to look into providing the scaffolding to interact with that in an Import Linter PR, go...

Also, I have been thinking about the other kind of cycle - the one that can happen between parents and children, and which `find_cycle_breakers` doesn't report on. IMO this is...

FYI, I think I have a working concept here now: https://github.com/seddonym/grimp/pull/253 Next steps are to add some more thorough tests, and possibly see if there is a way to avoid...

I'm pleased to say that I have now released the latest Grimp, which gives us [nominate_cycle_breakers](https://grimp.readthedocs.io/en/stable/usage.html#ImportGraph.nominate_cycle_breakers). I should have time to integrate this into the `acyclic` contract type, unless you...

> Thanks for updating me with a status and possibility to contribute. However, I think you should know better how to implement the remaining part from the import-linter side. Sounds...

Acyclic Siblings contracts are now available in the latest Import Linter. I'm very excited about this feature and have already started using it. Thanks @K4liber for making this happen! https://import-linter.readthedocs.io/en/stable/contract_types.html#acyclic-siblings

Hi! Thanks for reaching out. I don't totally understand the proposal yet though. Would you be able to provide an example of how this might behave?