What is the current behavior?
Today, if there are more than one intersection points between two curves/edges, there is no convention stablished about the order that intersection points are returned (it can be in the self or of the other instance, passed as argument, abscissa ascending order). This often requires additional verification steps in subsequent methods, introducing unnecessary complexity and potentially affecting performance.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages
What is the expected behavior?
I suggest adopting a convention to always return intersection points ordered by the abscissa of the self instance. This convention will not only enhance code readability but also eliminate the need for redundant checks in methods that utilize intersection results.
What is the motivation / use case for changing the behavior?Improve performance: We can try to code our methods respecting the convention adopted, reducing the needs of post-traitement
Reduced redundancy: With a standardized convention, there's no need for additional verification steps in methods that call intersection functions.
I'm submitting a ...
What is the current behavior? Today, if there are more than one intersection points between two curves/edges, there is no convention stablished about the order that intersection points are returned (it can be in the self or of the other instance, passed as argument, abscissa ascending order). This often requires additional verification steps in subsequent methods, introducing unnecessary complexity and potentially affecting performance.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages
What is the expected behavior? I suggest adopting a convention to always return intersection points ordered by the abscissa of the self instance. This convention will not only enhance code readability but also eliminate the need for redundant checks in methods that utilize intersection results.
What is the motivation / use case for changing the behavior? Improve performance: We can try to code our methods respecting the convention adopted, reducing the needs of post-traitement Reduced redundancy: With a standardized convention, there's no need for additional verification steps in methods that call intersection functions.
Possible fixes
Please tell us about your environment: