Deleted Comment
You do have to tag struct fields with a macro, but you can attach contexpr-visitable attributes. There's also a static limit to how many reflectable fields you can have, all reflectable fields need to be at the front of the struct, and the struct needs to be an aggregate.
- Build up the thinnest abstraction that lets you express a solution in the problem domain.
- Allow the API user to express their intent, and not be focused on mechanics they don't need to understand to get the job done.
- Focus on getting the interfaces right before the implementation is perfect.
- A clean interface will allow you to make drastic changes to the implementation without the API consumer becoming aware.
https://thinking-forth.sourceforge.net is worth reading, even if you have no desire to ever program any Forth.
I'm thinking of something that locks through a hole in the board and then pushes 4 pins onto 4 pads on the board.
Char peppers for peeling.
And promptly pointed out how community notes are being gamed when this happens.
Call me crazy but I don’t think the guy who routinely converses with Nazis will be applying his “free speech absolutist” ideals uniformly.
Elon routinely converses with Nazis? Which ones?