Jonas Santos Bezerra
Jonas Santos Bezerra
This will cause a major API change, so we need to discuss this better.
Question: should we also change the order of paramaters in the `compose` function to reflect **exactly** the category operator?
It makes sense. We could use `` https://www.haskell.org/hoogle/?hoogle=%3C%26%3E
About the integration of `FindMorphism` and `FinitaryCategory`: What would be the case for the Category **Graph**, which today only implements `FinitaryCategory`? Should we also implement `FindMorphism` for it (even though...
@ggazzi about your first comment: > "an application condition is essentially a constraint whose "antecedent-object" is the left-hand side of the rule" I don't think that applies, as only **atomic...
"Three blank lines between different sections of the source code." How about two, only? ^^'
@andrei529 this question should be on a different issue