Skip to content

Issues: propensive/acyclicity

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

3 Open 4 Closed
3 Open 4 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Consider alternative representation api Relates to the API design enhancement An improvement to existing functionality performance Relates to the efficiency or speed of an operation question Looking for an answer
#6 opened May 12, 2022 by propensive
@propensive
1
Maintain edges to a fixed "void" element in the internal representation code quality Concerns the standard of code rather than functionality enhancement An improvement to existing functionality minor Has only a small impact for the majority of users performance Relates to the efficiency or speed of an operation
#5 opened Dec 29, 2021 by propensive
@propensive
Add DagError when ill-formed graphs are produced beginner A good introduction for newcomers bug Describes something not working as intended code quality Concerns the standard of code rather than functionality enhancement An improvement to existing functionality severe Has a significant impact on many users
#2 opened Mar 21, 2021 by propensive
@propensive
ProTip! Mix and match filters to narrow down what you’re looking for.