Glaze as a reflection library

[fregate]

Hi @stephenberry !

I've really enjoyed using glaze as a json parser (and serializator, for sure).

For my project I have a few formats to receive and serialize to json, for example. One of these formats is Erlang binary term format. And I've realized that my current library is too... ugly, I guess, and slow in comarsion with glaze.

So I try to made glaze-reflection as underlying library for Erlang format and it works! I've made only a few changes in glaze to handle new format. But it works (only for read at this moment).

Do you think about split glaze (in fact it already splitted in core, json and beve) to "reflection library" and "format parsing"?

In any case, I put my repo here - If you would be so kind to check my glaze patch (thirdparty/glaze.diff) and applicable it to main repository (or make PR is better way to discuss these changes?)

https://github.com/fregate/termlib/tree/reflection

Thanks in advance

PS My current lib is, like, proof of concept (and I think, some constructions with template magic I'm not fully understand), but it works and I will improve it (writing, at least)

[stephenberry]

@fregate
Wow, this is really great! We've tried to design Glaze so that it is straightforward to add more formats. I would be happy to add you as a collaborator to Glaze so that you can push/pull to main and add support for the Erlang format.

I've recently made Glaze even better for developing new formats. Features like glz::custom just automatically work with any format in Glaze, this means you gain a ton of features for free when adding new formats.

Anyway, can I add you as a collaborator to Glaze? You could then pull Glaze, make a branch for Erlang from your code, and then create a pull request. I can look over your pull request and offer tips/explain the architecture more.

Reading is typically more complicated, so writing should be straightforward.

Also, the core reflection utilities in Glaze have become even more separated from formats since version 3, so your ideas here of splitting out utilities (reflection vs serialization) is very much a focus.

[fregate]

Hi, @stephenberry !

What a great offer! ) Be a part of this excellent library as a contributor! )

Right now Im on a vacation and in a few next weeks can't put some effort in. Sorry. But later - of course I will continue.

So I never was a contributor to community projects before - this will my first experience to create something useful and public available )

[stephenberry]

Cool! I sent you an invite. No rush on doing any of this, just let me know when you'd like me to take a look at your pull request. Have a great vacation!