4 ms·

First off, this is very cool! So don't let my comments dissuade you... But IME serialization tends to fall into two boats: 1. I want something akin to a confi

First off, this is very cool! So don't let my comments dissuade you... But IME serialization tends to fall into two boats: 1. I want something akin to a config that's human readable but very simple and I don't want to think about strong typing 2. I'm serializing data and I want schemas, efficiency, etc. I feel like (1) is pretty well handled by TOML and JSON and (2) is pretty well handled by flat/proto buffers, thrift/avro, capn' proto, etc. I guess I'm wondering where you see this being used.

alexrustic 3y ago
Thank you for your comment ! Jesth belongs to the first boat but on one condition: if you wish. If you need a section to represent a dictionary data structure, you should use the syntax designed for that, so you can later call the section's "make_dict" or "get_dict" methods to convert the raw lines (list of strings) in an object dictionary. You are free to create your own hacks to convert a raw section into an object that suits your needs. About boat 2 schemas, I'm thinking of designing a type validation schema, much like what we do when creating tables with SQL.