Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
So it seems like the in-vogue thing on c++ twitter these days is to talk about reflection. The solution developed for a personal project I am involved in accomplishes constexpr reflection in c++17. Here is a little sample and a few thoughts on it's designpic.twitter.com/z42QjoVAMx
1) Yes, we're using the preprocessor. Best tool c++ has at the moment. 2) Reflection macros are intentionally outside the declaration. I may not want to reflect all members of a struct. I may want to reflect a 3rd party lib's structs.
3) It's all known at compile time, so you can even type deduce based on whether a struct has a member by a certain name, type, or offset. 4) Supports structs, enums, dynamic arrays (vectors), and strings. Plans to support variant-likes and associative containers.
5) We intentionally don't support pointers and references. I don't find much value in reflecting them, although it wouldn't be difficult to do so.
6) Despite using the preprocessor, aesthetic was also important to us. BEGIN()/END() macros are ugly. Wanted something sleek, native-feeling. I think we mostly accomplished that.
As an aside, Circle has been showing off attributes recently. I think this system can pretty easily expand into that. As a bonus, we could add attributes to a 3rd party lib's structs. Not sure if circle can support that the way they implement attributes.
This is how I envision attributes being added. Some unknowns yet, but I think it's doable.pic.twitter.com/31PVjVzjNH
Proper reflection, when c++ finally gets it, is going to change so much. I am tweeting about this to point out how far we can get already. It's not as pretty, but still very serviceable.
Oh, forgot to mention! The core reflection header is ~ 500 LOC with comments. It does use a few of our in-house classes and utilities. If it were made standalone, probably 800 LOC with comments.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
