Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Hi, thanks for the comments. Getting entire C++ standard library covered was the original intent :). But as I said, if people find it useful, I will be more than happy to revive it and hopefully achieve the original goal. As far as documentation concerned, README was suppose to serve that purpose. I tag each test and the README.md is auto generated every time the project is compiled and run. But I understand it may need work. I may rethink the tagging and may generate separate "Table of contents" views. For example there may be a view that is strictly alphabetical, another one that has C++ standard table of contents etc. I have to think about it.
oh yes definitely, but I meant more the particular way I've done it so far - which has been to implement something similar to boost::hana::is_valid(), to make it take the least amount of boilerplate code per-use-case as possible: zero additional lines of code.
Related posts
- Simple `struct` static reflection system I use that tracks names, attributes (in my own code I also keep `constexpr` hashes of names) -- example gets fully inlined into `main()`
- C Implementation Challenge Replacing Stdmove And
- Potential C++ extension for type erasure as a language feature
- Dyno: Runtime Polymorphism Done Right
- How portable is ST's HAL API?