Skip to content

Think hard about QuadTrees #26

Description

@Maxopoly

Dan said:

little silos, intent is subdivided and not everyone groks the same aspects to the same degree
and the knowledge is lost over time
net effect is that the QTBox winds up behaving like a quandrant grab bag, and total ordering just isn't necessary on its members, they just need to be 2-axis comparable
so from that POV I agree with you that some-other-set is just as fine
and removing the total ordering req is not counter the current implementation
but it probably does run counter the original intent, if I'm looking carefully
🤷
6 or half dozen, yanno? which is more useful?
just, damn, so many better ways to do this using a treeset
(in terms of Quad stuff)
like, using TreeSet.Before() using a special element, b/c everything is organized internally as NW before NE before SW before SE. So you can easily extract whole quadrants using treeset ops without needing to fully iterate
stuff like that
fix-scope-creep!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions