People often bring up the idea of automatic type-erasure by reflecting on C++20 concepts. While I agree that type-erasure based on Generic Programming concepts is a solid idea, C++20 concepts are far from that. To properly do this, we'd basically need to turn C++ into @SwiftLang
-
-
Less a problem of reflection, more the shortcomings of C++ concepts: arbirtrarily complex usage-patterns, often opaque requirements through traits, minimal associated-type support. We can likely do simple things, but without major changes we'll likely not get "virtual concepts".
-
Alternatively, though, with reflection we can still achieve similar goals, but it will likely not be through introspection of a C++ concept. It would more likely be through introspection of something more akin to a protocol.
- 1 more reply
New conversation -
-
-
Please see my message about Marcus Tolbert 8 year old from Rochester, MN
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.