jpmag
Well, you're not doing anything wrong. But it's also not a bug -- rather a byproduct of required behaviour. There are several factors leading cumulatively to this: - When parsing,...
In #543 some functions are added to make this easier. You can now clear the style with a single call: ```c++ auto tree = parse_in_arena(to_csubstr("{\"foo\": \"bar\"}")); tree.rootref().clear_style(/*recurse*/true); assert(emit_yaml(tree) == "foo:...
Thanks for the detailed report. I was able to reproduce. Hold on while I investigate, and hopefully fix.
Did you set the error handler? The error message you see comes from the error handling code, which will subsequently result in a call to the error handler. The default...
I was able to reproduce the SIGABRT; hold on while I investigate.
Thanks for reporting! There seems to be a problem: while parsing, the callbacks from the tree are overwritten with those from the event handler. It will be some time until...
Please leave this open.
> I found the c4core required gcc 5 and cmake 3.15 This does not seem right. Both c4core and rapidyaml are successfully tested in gcc 4.8: see relevant [CI run...
> here is why gcc 5: Which version were you using? That line was last changed in 2022. See [current version](https://github.com/biojppm/c4core/blob/f6acc1d3eb5b61b4cfe75ec67c5a7a2beee59e8a/src/c4/compiler.hpp#L105) > here is why cmake 3.15 That's a test...
You are adding temporaries to the tree. Thereafter, python is free to delete or overwrite those temporaries, but the tree will still be referencing their (now stale) memory! The first...