Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Type error for uncomposable morphisms #121

Open
agureev opened this issue May 8, 2023 · 1 comment
Open

Type error for uncomposable morphisms #121

agureev opened this issue May 8, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@agureev
Copy link
Collaborator

agureev commented May 8, 2023

We need to upgrade the comp functionality so that it does not allow to compose things with non-matching (co)domains and tell us exactly where the error occurs. This will make troubleshooting much easier.
@agureev agureev added the enhancement New feature or request label May 8, 2023
@agureev
Copy link
Collaborator Author

agureev commented Aug 4, 2023

#138 aids this by supplying a well-defp-cat function returning t iff a morphism is well-defined. This can be easily incorporated into the pipeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@agureev