-
Kenton Varda authored
That is to say, whereas previously we would extend capnp::typeId<T>() to a new type by declaring a specialization of it for that type, now we instead have the type contain a nested class called _capnpPrivate which contains a `typeId` constant. This is necessary because it is impossible to specialize a template for a type which is itself nested inside a template type. E.g. it's impossible to write a specialization `template <typename T> typeId<Foo<T>::Bar>()`; C++ simply doesn't support this. But with generics, Cap'n Proto will allow types to be nested inside templates, so we need this to work.
490acec8
Name |
Last commit
|
Last update |
---|---|---|
c++ | ||
doc | ||
highlighting/qtcreator | ||
.gitignore | ||
CONTRIBUTORS | ||
LICENSE | ||
README.md | ||
RELEASE-PROCESS.md | ||
mega-test-quick.cfg | ||
mega-test.cfg | ||
mega-test.py | ||
release.sh | ||
super-test.sh |