4 ms·

What features would you like to see added soonest in your favorite C++ compiler?

12 points by AndreyKarpov 14y ago

deleted 14y ago
[deleted]
tbirdz 14y ago
I'd like to see better template error messages.
- archangel_one 14y ago
  I've done quite a lot of C++ programming and can generally work my way through template error messages, but still totally agree - it would be much nicer if I didn't have to. Even if it can't be solved generally (which seems likely since nobody's done it yet) just some special casing for STL containers and algorithms would go a long way.
- Someone 14y ago
  Have you seen the "template type diffing" (http://clang.llvm.org/diagnostics.html http://clang.llvm.org/diagnostics.html) in clang?
deleted 14y ago
[deleted]
J_Darnley 14y ago
It's not my favourite compiler, I don't even use it, but I would like to see C99 support added to one.
- sanxiyn 14y ago
  Same here, but we are in the minority. http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and-c99/ http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and... We do not plan to support ISO C features that are not part of either C90 or ISO C++. I understand C programmers may be disappointed or angry with this answer and I'm sorry to have to say no here. It's true, and very quotable, that "focus means saying no," but that doesn't make it easy to say -- it is hard to say no to you, and I'm sorry to say it. But we have to choose a focus, and our focus is to implement and innovate in C++.
ambrop7 14y ago
Static If [1]. Would simplify a lot of template code, like generic data structures with optional features. template <class Entry, bool useParents> struct AvlTreeHelper { int balance; Entry \child[2]; static if (useParents) { Entry \parent; } }; template <...., bool useParents> void ...::insert (...) { ... static if (useParents) { // fixup parent pointers } ... } Such optional behavior can be achieved with existing C++ features by inheriting specialized template classes, but it makes code very unreadable, especially when you have big functions with small conditional parts inside, or when you have more than one boolean condition. [1] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3329.pdf http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n332...

12 points by AndreyKarpov 14y ago

deleted 14y ago

[deleted]

tbirdz 14y ago

I'd like to see better template error messages.

archangel_one 14y ago
I've done quite a lot of C++ programming and can generally work my way through template error messages, but still totally agree - it would be much nicer if I didn't have to. Even if it can't be solved generally (which seems likely since nobody's done it yet) just some special casing for STL containers and algorithms would go a long way.
Someone 14y ago
Have you seen the "template type diffing" (http://clang.llvm.org/diagnostics.html http://clang.llvm.org/diagnostics.html) in clang?

deleted 14y ago

[deleted]

J_Darnley 14y ago

It's not my favourite compiler, I don't even use it, but I would like to see C99 support added to one.

sanxiyn 14y ago
Same here, but we are in the minority. http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and-c99/ http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and... We do not plan to support ISO C features that are not part of either C90 or ISO C++. I understand C programmers may be disappointed or angry with this answer and I'm sorry to have to say no here. It's true, and very quotable, that "focus means saying no," but that doesn't make it easy to say -- it is hard to say no to you, and I'm sorry to say it. But we have to choose a focus, and our focus is to implement and innovate in C++.

ambrop7 14y ago

Static If [1]. Would simplify a lot of template code, like generic data structures with optional features. template <class Entry, bool useParents> struct AvlTreeHelper { int balance; Entry \child[2]; static if (useParents) { Entry \parent; } }; template <...., bool useParents> void ...::insert (...) { ... static if (useParents) { // fixup parent pointers } ... } Such optional behavior can be achieved with existing C++ features by inheriting specialized template classes, but it makes code very unreadable, especially when you have big functions with small conditional parts inside, or when you have more than one boolean condition. [1] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3329.pdf http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n332...