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.

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

LazyPolygonWindingOrder #175

Open
asinghvi17 opened this issue Jul 13, 2024 · 2 comments
Open

LazyPolygonWindingOrder #175

asinghvi17 opened this issue Jul 13, 2024 · 2 comments

Comments

@asinghvi17
Copy link
Member

No description provided.

@rafaqz
Copy link
Member

rafaqz commented Jul 29, 2024

So we prepare a polygon with a BitVector of ring order and then check it in getpoint? It would be faster for GI.getpoint(ring, i) if it was in the type but that could cause issues, especially if they're not all the same order.

@asinghvi17
Copy link
Member Author

That could work - since this is a one-off special case I'm tempted to say we should create a specific type for this, so dispatch is easier, and we don't have to overload the preparation interface more. And this is more of a fix than a preparation anyway...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants