Skip to content

Are all the fields in the RTree struct necessary? #31

@asinghvi17

Description

@asinghvi17

None of them seem to be accessed at any point, only the index is. We could potentially make the RTree struct vastly simpler by allowing a keyword constructor + forwarding some methods to rtree.index, and doing the following:

struct RTree
	index
	ndims::Int
	lock::ReentrantLock
end

and then having a massive constructor with all keyword arguments available, as well as potentially overloading set/getproperty.
Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions