Hi all,

I have a relatively extensive programming background, but I am new to Rust.
In recent days, I have written a library and a program for Nav Graph pathfinding with A*.
This program compiles without warning, and Clippy does not report one either:

My questions are now:

1. Does the Code in any part deviate from common Rust programming best practices, and if so, where?
2. Do you see any parts that are very inefficient concerning the Rust programming style?
3. Besides the core A* implementation, the library also contains a lot of stuff to make an interactive application of it, to demonstrate and test the functionality. If something like this were submitted to crates.io, would it be advisable to keep the interaction test/demonstration part, or would it be preferred to separate this and only submit the core part with the unit tests?

Thanks for any info on these subject matters,
Christoph

1 post - 1 participant

Read full topic