To be discussed:
I am not quite satisfied with the interface yet:
Log{"msg"}("key",val)("key2",val2)
is not super nice.
I like [] better but this is only avaliable in c++23.
Also map interface has too many brackets in my opinion:
Log{"msg"}({{"key",val},{"key2",val2}})
Best solution would be designated initilializers like:
Log{"msg"}(.key=val, .key2=val2)
But for this I would need reflections to turn the struct fields into json, perhaps possible with c++26...
Checklist before requesting a review
[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.
[ ] If this is a new component I have added examples.
[ ] I updated the README and related documentation.
Description
As discussed in https://github.com/olympus-robotics/hephaestus/issues/86 we want to make the logging more scalable. This is a proposal for adding structured logging. Done:
To be done:
To be discussed: I am not quite satisfied with the interface yet: Log{"msg"}("key",val)("key2",val2) is not super nice. I like [] better but this is only avaliable in c++23. Also map interface has too many brackets in my opinion: Log{"msg"}({{"key",val},{"key2",val2}}) Best solution would be designated initilializers like: Log{"msg"}(.key=val, .key2=val2) But for this I would need reflections to turn the struct fields into json, perhaps possible with c++26...
Checklist before requesting a review