StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In your case, the only way that I see would be to explicitly specialize <code>MyClass</code> for <code>InheritSomeTag</code>. However, the <a href="http://www.biomedcentral.com/1471-2105/9/11/abstract" rel="nofollow noreferrer">SeqAn paper</a> proposes a mechanism called “template sublassing” that does what you want – albeit with a different inheritance syntax, so the code isn't compatible with your current <code>main</code> function.</p> <pre><code>// Base class template <typename TSpec = void> class SomeTag { }; // Type tag, NOT part of the inheritance chain template <typename TSpec = void> struct InheritSomeTag { }; // Derived class, uses type tag template <typename TSpec> class SomeTag<InheritSomeTag<TSpec> > : public SomeTag<void> { }; template <class T, class Tag=T> struct MyClass { }; template <class T, typename TSpec> struct MyClass<T, SomeTag<TSpec> > { typedef int isSpecialized; }; int main() { MyClass<SomeTag<> >::isSpecialized test1; //ok MyClass<SomeTag<InheritSomeTag<> > >::isSpecialized test2; //ok } </code></pre> <p>This certainly looks strange and is very cumbersome but it allows a true inheritance mechanism with polymorphic functions that is executed at compile time. If you want to see this in action, have a look at some <a href="http://www.seqan.de/dddoc/html/INDEXPAGE_Demo.html" rel="nofollow noreferrer">SeqAn examples</a>.</p> <p>That being said, I believe that SeqAn is a special case and not many applications would profit from this extremely difficult syntax (deciphering SeqAn-related compiler errors is a real pain in the *ss!)</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload