petgraph
prepona
| petgraph | prepona | |
|---|---|---|
| 7 | 3 | |
| 2,834 | 87 | |
| 1.9% | - | |
| 6.3 | 0.0 | |
| 20 days ago | 11 months ago | |
| Rust | Rust | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
petgraph
-
Borrow Checking, RC, GC, and the Eleven () Other Memory Safety Approaches
Are you just trying to throw shade on Rust?
https://doc.rust-lang.org/std/collections/struct.LinkedList....
> NOTE: It is almost always better to use Vec or VecDeque because array-based containers are generally faster, more memory efficient, and make better use of CPU cache.
https://docs.rs/petgraph 78 M downloads
-
The Hunt for the Missing Data Type
I used to think that since graphs are such a broad datastructure that can be represented in different ways depending on requirements that it just made more sense to implement them at a domain-ish level.
Then I saw Petgraph [0] which is the first time I had really looked at a generic graph library. It's very interesting, but I still have implemented graphs at a domain level.
[0] https://github.com/petgraph/petgraph
-
Many of the typical "Algorithms" as plain Rust implementation
For graph algorithms specifically, also consider looking at the implementations in petgraph.
-
2-way Weak
Take a look at: https://github.com/petgraph/petgraph
-
autograph v0.1.0
Render the backward "graph" using petgraph for visualization and debugging purposes.
-
Another graph library :)
I second the need for quickcheck-style tests. I implemented a matching algorithm in petgraph, and quickcheck discovered so many bugs on non-trivial graphs. Thanks to it, I am now much more confident that it is indeed correct.
-
Why Rust for Robots?
petgraph: Graph data structure library, compatible with Rust
prepona
-
Design problem | Too many generics!
I'm currently working on a redesign of my graph library(on the 0.2 branch). I've been trying to take inspiration from different graph libraries. I like how the boost graph library is highly parameterized. So I've been trying to take this into account while designing and implementing different parts of the library.
-
Another graph library :)
But here it is https://github.com/maminrayej/prepona.
What are some alternatives?
autograph - A machine learning library for Rust.
rosrust - Pure Rust implementation of a ROS client library
optimization-engine - Nonconvex embedded optimization: code generation for fast real-time optimization + ROS support
openrr - Open Rust Robotics
graph-force - Python library for embedding large graphs in 2D space, using force-directed layouts.
nphysics - 2 and 3-dimensional rigid body physics engine for Rust.
ros2_rust - Rust bindings for ROS 2
rustros_tf - A port of ROS's TF library to rust
rust-gpu - 🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧
KLighD - KIELER Lightweight Diagams
Rust - All Algorithms implemented in Rust