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
Integration of space into the rustsim organization. #22
Comments
Thank you for giving me some pointers on what is necessary to add the library to rustsim. This weekend I should have some time to start hacking at some of these things. Clearly more work does need to be done here to transport the library into something really usable (like good documentation). I will start by pulling off some of the documentation and test related issues first before trying to bite off combining the partitioning module from ncollide in a way which unifies the ways the spatial tree is queried. Once I get to that part I will start opening the relevant issues.
I will look into that.
Please do! I haven't properly tagged my issues yet, but many of them are simply building out new spatial tree types. I can look into tagging them appropriately based on difficulty. |
Status updateI am currently loaded up with fixing up photogrammetry crates in the Rust community. I will eventually finish that, get back to a hamming weight tree datastructure I am writing (and speeding up), then finally I intend to make the So, I really do want to get back to this, but I am down in the weeds of Rust photogrammetry for the time being until there are usable tools for those things. I think I can probably make the abstractions here in about 1-3 months, which will just depend on what order things happen in. I do intend to work on |
Hi @vadixidav!
This is a follow-up to our discussion on Discord regarding the potential integration of
space
into the rustsim organization.While currently light, the feature set of this crate are very useful, and its long-term goals interesting. After reviewing this project, here are a some improvements we could work on before actually adding
space
to the rustsim organization. This is a macro list, which could be broken down into several smaller issues. Of course, everything is open to discussion:#![deny(missing_docs)]
directive. Everything in the crate should be documented, even if it is minimal.space
. I think it is best to think about it from the beginning since it is pretty overwhelming to have to add them all at once after the crate grows.Linear
andPointer
were replaced by something likeLinearOctree
andPointerOctree
.Doing all this will probably take a fair amount of time (perhaps a couple of months) but I think this is worth it as it will increase the quality of this crate and its documentation. I will contribute too of course.
If that's okay with you, I will link this issue into the next monthly rustsim newsletter so potentially attract contributors.
The text was updated successfully, but these errors were encountered: