Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
The RustSec Security Advisory Database includes "informational advisories" about unmaintained crates, and when possible, includes recommendations for maintained alternatives.
Some context, In my day job, I'm working on a custom format that is based on yaml but extends it. We're still using C++, so we the used yaml-cpp as a base for our parser and it was great for that purpose. laying with rust on Advent of Code lately I also got sent back to reality... Not having rust enums, match, great string handling, iterators when working with my AST was hard. So I wanted to try to implement the same parser in Rust as an example to my teammates of how great rust can be.
The first thing I did was to find the crate yaml-rust and it seems it isn't really maintained anymore. It has not been updated in a year and there's a lot of PR's and unresolved issues, the CI is broken... So here is my open ended question.
But there seems to be already a lot of forks, and I'm not convinced it is the best solution, there still would be dozens of repos using yaml-cpp and not would not benefit the dozens of repos that depends on it. Imagine someone creates a great fork, would it be possible to move ownership of the crate on crates.io to this new fork? (to me it seems really difficult without some sort of comity ruling this).
An example https://github.com/kmcallister/syscall.rs/network/members
Related posts
- Serde-YAML for Rust has been archived
- Why do we need configuration? Creating and handling configuration files in Rust
- Introduction to Rust generics [1/2]: Traits
- Weird error only on android: "this struct takes 3 generic arguments but 2 generic arguments were supplied" for serde_json
- Getting Started with Hippo - a WebAssembly PaaS (Part 3)