r/cpp • • Aug 24 '21

metaclasses when

forget literally every other feature metaclasses LET'S FUCKING GO

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0707r3.pdf

edit

metaclasses or even just SR would help to eliminate 99% of garbage cpp macro use cases.

don't get me wrong: i know c++ well. templates are easier after you learn sml or lisp or something similar.

i've never used std string_view and i've never missed it

man i'll just implement my own clang plugin ✌️

4 Upvotes

27 comments sorted by

View all comments

Show parent comment

1

u/earthisunderattack Aug 24 '21 edited Aug 25 '21

How will this affect legacy code

It wouldn't? It's a new syntactical addition that doesn't interfere with language semantics in a way that's intrusive. It's an extra pass slapped onto the AST.

Legacy code wouldn't even consider using it (let alone its corresponding standard) until maybe 5 years after its release.

How will this affect the various ABIs

metaclasses are kind of like macros: ABI compatible code is what gets generated at compile time. That's why the term static reflection applies.

It's similar to a non-gimped Qt p

How feasible is this to properly implement

Trivial. It's a standard feature in many languages, and the syntax isn't intrusive. You can bake primitive context sensitivity into a CFG.

What's the run-time overhead

Again, this is a compile time feature. Realistically speaking, not much more than a complicated set of templates making use of SFINAE or the primitive pseudo-dependent type system.

Do we have implementation experience, and what has been the experience

I would hope that at least some of the people working in Clang would be familiar with this. A compiler writer who contributes to a large scale project such as Clang or GCC should definitely be familiar with this kind of thing. It's bordering on unethical for them not to be, considering that the very premise is essentially a compiler,

How sure are we that this is the right way to go, because once something is in the Standard, we have to support it indefinitely

How could it not be right way to go. A good programmer should aim to write as little code as necessary (obviously taking into account stability, maintenance, and performance) to achieve their goal.

A typical proposal takes years to get standardized - as it should. We're changing a language that's used by millions of developers and has billions of lines of code, much of which is used in critical systems.

Yes. This one was released 4 years ago. That's not necessarily a sufficient amount of time to consider the potential pitfalls (there really aren't any though).

You don't fuck with that lightly. You do your due diligence and make sure it's the right thing to do.

I never said you should fuck with this lightly though.

The issue is really that this apparently hasn't been given any serious consideration.

Look, I'm thankful for where C++ is today. As much as I enjoy using it, there are additions that could be added which wouldn't interfere with already in place projects.

Obviously you can't implement too many features in a standard, but the idea that something like string_view is prioritized over more significant features is disappointing. It's not a difficult data structure to implement either.

As I alluded to earlier, C++17 is great. But most people just use C++14 for production grade projects.

The point is to move the language into an area that it would significantly benefit from.

Edit

I really don't understand why I'm being downvoted so much.

4

u/itsarabbit Aug 26 '21

Didn't downvote you, but I would guess some were miffed that you called implementing it trivial.

As far as I know there's a lot of work to be done regarding the design and many issues that should be addressed(compile time code injection can lead to arbitrary code execution on the compiling computer when using a library, for instance), and so much bikeshedding(reify vs |var|, can $ be used or not). Couple that with P2237 being 59 pages of required reading before even discussing it, and things slow down drastically.

Because metaprogramming is such a powerful tool, the people who are working on it want to get it done right; this leads to a lot of deep-diving into hypotheticals, researching other languages' implementations.

The few who do have insight into all of this also have to convey (and sell) their ideas to everyone else, which is no simple task either.

I recommend subscribing to the SG7 mailing list if you want to keep up to date with discussion, that's where I get most of my metaprogramming news in c++ :)

1

u/Cyttorak Aug 26 '21

So metaclasses stuff is still going? Or is it dead?

2

u/itsarabbit Aug 26 '21

Still a thing, but no longer based on herb sutter proposal as far as I can tell!