Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 59
    Oh great, I hadn't seen this part of C++0x and I've been bitching about templated typedef for a while... guess I should have a more thorough read of the final draft. Commented May 9, 2010 at 11:19
  • 3
    Will inheriting constructors make the OP's original solution are more viable solution? Commented Aug 24, 2012 at 6:07
  • 3
    @StackedCrooked: Depends on his goals. I avoid inheritance when composition will do (and yeah, inheriting constructors will make both of these easier), but I also avoid composition when a typedef will do. Commented Aug 24, 2012 at 14:34
  • 3
    using does not support specialization if I'm not wrong, so the second option is still useful in many cases. Commented Feb 3, 2016 at 14:27
  • @UtkarshBhardwaj Notice you can combine the two, similar to the way that <type_traits> contains alias declarations such as std::remove_reference_t the refer to various specializations of std:::remove_reference. Commented May 5, 2021 at 13:01