Re: [boost] typedefs within Concept or as Trait?

Doug Gregor <dgregor <at> osl.iu.edu> writes:

Traits classes are far better than nested typedefs, because one can always specialize a traits class for an existing type---even if you can't modify the type because it is built-in or comes from another library that you can't modify.

This is not exactly true if typedefs are part of some concepts types used as a policies, right? This is true is we are talking about typedefs as members of your primary template parameter type.