> > Reflection proposals (these are very early-stage proposals, but they > > give an idea of the directions people are exploring): > > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3987.pdf > > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3996.pdf > > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4027.pdf > > I was just going to write and propose something in this direction. > > My hope is that this could do things like enable us to at compile-time > enumerate the list of members and their types, and use that to > generate cycle collector functions. As well as cause build-time > failures if a cycle collected object contains any members which we > don't know how to traverse/unlink. > > Similarly, by enumerating the list of base classes we could generate > the code for QueryInterface. > > Automatic generation of serialization/deserialization code for IPC is > another potential candidate.
These categories of use cases are definitely within the scope of the Reflection Study Group's work! N4027 got strong positive feedback when presented, and may well turn out to be the foundation of reflection libraries that are suited to the above tasks. Cheers, Botond _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
