petgraph
chatgpt-ifplatform
Our great sponsors
petgraph | chatgpt-ifplatform | |
---|---|---|
7 | 1 | |
2,648 | 0 | |
4.8% | - | |
7.0 | 3.2 | |
2 days ago | 12 months ago | |
Rust | C# | |
Apache License 2.0 | Apache License 2.0 |
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
chatgpt-ifplatform
-
The Hunt for the Missing Data Type
It's really an experimental endeavor. I have a Github repo (https://github.com/ChicagoDave/chatgpt-ifplatform), but I'm still changing things all the time. It's very volatile.
Finding the balance between OO principals, Fluid coding capabilities, separating the data, grammar, parser, and world model and then constructing a standard IF library of common IF "things" is like juggling 20 kittens and 10 chainsaws.
Some things are confounding like do I define a container with a boolean property on an object or is a container a subclass of the base Thing? How does that extend to the underlying graph data store? What will queries look like and which solution is more meaningful to authors?
Seriously, 95% of the fun is figuring all of these things out.
What are some alternatives?
autograph - 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
prepona - A graph crate with simplicity in mind
nphysics - 2 and 3-dimensional rigid body physics engine for Rust.
graph-force - Python library for embedding large graphs in 2D space, using force-directed layouts.
openrr - Open Rust Robotics
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 🚧
Rust - All Algorithms implemented in Rust