News for hackers. Stuff that matters.

A comment on Fun with C++26 reflection: Keyword Arguments. Parent comment

Re:Fun with C++26 reflection: Keyword Arguments by flohofwoe on Tuesday February 11, 2025 @02:59AM (#43010185)
I'm in the opposite camp, runtime reflection is useless, and almost always points to a design flaw while compile time reflection is actually useful (for obvious things like automatically building a serialization layer or an UI which represents the type, or building types from other types).

I'm sure that C++26 has implemented it in a way which is highly unpleasant to use though ;)

[ Parent | on HN ]
Re:Fun with C++26 reflection: Keyword Arguments by jcranmer on Tuesday February 11, 2025 @09:59AM (#43013486)
The element of runtime reflection that is the most useful is something along the lines of "here's function, here's a list of arguments, go call this function with those arguments".
[ Parent | on HN ]
Re:Fun with C++26 reflection: Keyword Arguments by xmcqdpt2 on Wednesday February 12, 2025 @07:04AM (#43024492)
Having to do this by reflection is a problem in principle solvable by types. Here is a function of type (A, B, C) => R, and here is a tuple of arguments of type (A, B, C), go call this function with those arguments.

Most programming languages make it hard to easily express those constraints so reflection is used instead.

[ Parent | on HN ]