yaml-cpp VS rapidyaml

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)

Interesting, I hadn't come across extism before. How hard would it be to package https://github.com/biojppm/rapidyaml in this way? (And do you have a extism for dummies guide?)

The inability, or brittleness, to embed NUL bytes into the string, for once. Zeroed bytes can be valid as an internal bytes of a longer encoded character. And the inefficiency of tempting every caller to rederive the string length on every use, leading to such bugs as quadratic parsing behavior with sscanf. The extra register for an explicit length is a very minute price to pay compared to that.

Although you still have the other problem of sscanf, where read times can become quadratic.

You are really simplifying that issue. A lot of it has to be how the implementation of sscanf works and it's super easy to abuse by complete accident when a lot of data needs to be read and parsed to correct values. See more here: https://github.com/biojppm/rapidyaml/issues/40

Leading to eye-rolling problems like these: https://github.com/biojppm/rapidyaml/issues/40