Protobuf VS cereal

This is doable via this trick:

https://github.com/protocolbuffers/protobuf/blob/ae0129fcd01...

Install the protoc compiler manually from here and add it to your PATH.

We wanted to use Ractors in our latest Ruby project (which is Rust based using rb-sys/magnus for some parts), but since our users use Google Protobuf inside the code that may run in Ractors, we could not because the library is not Ractor safe[0] (and it's unreasonable for us to ask our users to not be able to use the official Protobuf library).

0 - https://github.com/protocolbuffers/protobuf/issues/19321

For Java, I think you mean Jackson, not gson, unless something has changed recently. Goes to show that even the behemoths can get this wrong.

https://github.com/protocolbuffers/protobuf/blob/6aefdde9736...

Building Neon requires 3.15+ version of protoc (protobuf-compiler). If your distribution provides an older version, you can install a newer version from here.

Best bet is likely https://github.com/protocolbuffers/protobuf/blob/main/docs/f..., which predates editions.

Protocol Buffers Documentation protobuf Json JSON in API Development

You can also download the protoc compiler from the official protobuf release page and add the path to the protoc compiler to the system environment variable.

I'd stick with cereal for serialization

Today I'm back to working on Pataro, the roguelike built on libtcod that made up much of my Hacktoberfest efforts. I had been assigned to an issue requesting the addition of serialization and deserialization, but unfortunately ran out of time and wasn't able to finish the former or start the latter. I ran into issues with Cereal, and had a hard time figuring out the structure of the program and how to go about implementing serialization for all the relevant components. At the end of that attempt I mentioned that if I were to try again I'd start by testing out Cereal separately and getting a handle on that before trying to implement it in Pataro - so that's what I'm doing today.

I am once again working on Pataro today, and I've succeeded in clearing up some issues and creating new ones. I've been stuck on an issue where Visual Studio was raising errors in the portion of the code where I call the cereal archive on some types, but was able to clear up that issue by moving the save function definitions out of their respective headers and into the corresponding .cpp files. Examining this repo and its use of cereal again, I was able to get a bit clearer of an idea of how it's implemented, and I included just about every relevant cereal header I could find to try and avoid any issues like the previous one popping up again (with the intention of later removing whichever I can to avoid redundant inclusions).

On the Pataro front, I've started looking at other examples of people using cereal for their games. It seems to be a popular choice for roguelike games like this, so hopefully I can figure out both the syntax problems I'm facing, as well as logical ones like how the program should be structured to have all the necessary data properly serialized and deserialized.

Progress on one front but roadblocks on another. After my post yesterday outlining my plans to add serialization to Pataro I ran into some issues with calling the archive class in cereal wherein the call wouldn't go through due to an incorrect number of arguments. This happened with both vector and size_t data members, and I'm still investigating why.

This is the simplest serialization library I saw. You only need to add one method to your class and you can stream it to desired archive. It supports binary as well as json, XML and others. https://github.com/USCiLab/cereal