We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
I think that the current representation of literal lists as for example seen in cell 35 of https://github.com/homalg-project/CategoricalTowers/blob/f9066b25c0c46765b46bc31941dea427fe85cbf5/FiniteCocompletions/examples/notebooks/CartesianDiagonal.ipynb is quite misleading. I suggest to create separate nodes labeled "[ ... ]" for literal lists in the tree. In this example, there would be two separate nodes collecting the arrows 1 and 2 and the arrows 4 and 5 in the input of "UniversalMorphismIntoDirectProduct..." into two literal lists.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I think that the current representation of literal lists as for example seen in cell 35 of https://github.com/homalg-project/CategoricalTowers/blob/f9066b25c0c46765b46bc31941dea427fe85cbf5/FiniteCocompletions/examples/notebooks/CartesianDiagonal.ipynb is quite misleading. I suggest to create separate nodes labeled "[ ... ]" for literal lists in the tree. In this example, there would be two separate nodes collecting the arrows 1 and 2 and the arrows 4 and 5 in the input of "UniversalMorphismIntoDirectProduct..." into two literal lists.
The text was updated successfully, but these errors were encountered: