Thanks for this link. Between it and the main article, I have a much better sense for how compile time reflection will actually be useful. The syntax is bad enough to make my eyes bleed, but at least they'll bleed for a good reason I hope.
Thanks for this link. Between it and the main article, I have a much better sense for how compile time reflection will actually be useful. The syntax is bad enough to make my eyes bleed, but at least they'll bleed for a good reason I hope.
> The syntax is bad enough to make my eyes bleed
That's on brand for C++ in general. It works well, but it's ugly as sin while doing it.
I don't agree with you. Yes syntax is often awful but no it doesn't work that well. It's a minefield of Undefined Behavior.
While true, just like everyone on Rust land rarely thinks about configuring their projects without clippy, C and C++ developers should learn static analysers for C and eventually C++ exist since 1979.
It doesn't fix everything, yet it fixes more than those that don't use them at all.
I have been using such tools since mid-1990's when coding in either C or C++, and sadly it is still a discussion point regarding adoption.
I am happy^^ that ^^ is our quote character. ^^