yaml-cpp VS crates.io

FetchContent_Declare(yaml-cpp GIT_REPOSITORY https://github.com/jbeder/yaml-cpp.git GIT_TAG yaml-cpp-0.7.0 GIT_SHALLOW TRUE ) set(YAML_CPP_BUILD_TESTS OFF) FetchContent_MakeAvailable(yaml-cpp)

As you can see, I'm trying to coerce some YAML::Node to get some unknown type:

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.

yaml-cpp

Hi, this is a library (https://github.com/jbeder/yaml-cpp), I tried to add it but unfortunately I can't, and I can't find any instructions.

cmake_minimum_required(VERSION 3.0.0) project(cmaketest VERSION 0.1.0) include(CTest) enable_testing() include(ExternalProject) ExternalProject_Add(yaml PREFIX 3rd_party GIT_REPOSITORY https://github.com/jbeder/yaml-cpp/ INSTALL_COMMAND "" ) add_executable(cmaketest main.cpp) set(CPACK_PROJECT_NAME ${PROJECT_NAME}) set(CPACK_PROJECT_VERSION ${PROJECT_VERSION}) include(CPack)

I've found is yaml-cpp. The API seems fine

If you want a file format that has more readability, YAML is probably your best bet.

Can this not be parsed as YAML? (https://github.com/jbeder/yaml-cpp)

All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.

So this is my question: Which way was the right to find it out? There is no info about this feature on crates.io. I also have no clue what exactly it does and why it is named rwh_05.