> There is a Reflection Study Group (a sub-group of the Committee which > focuses on a particular area) which is tasked with investigating > language and library extensions for compile-time and runtime reflection. > The majority of the interest so far has been for compile-time reflection, > but I believe some of the infrastructure for compile-time reflection > will enable runtime reflection as well. > > The Reflection Study Group met in Chicago last week, and talked about > a rough outline of the sorts of things C++ programmers would like to > be able to do with reflection, from straightforward things like > iterating over the members of a class at compile-time for purposes > such as serialization and equality comparison, to more sophisticated > things like synthesizing new types by transforming existing types. > > I believe the plan is to issue a call for proposals, with some > guidance about the general direction that is desired, derived from > that outline. The Study Group will then look at the proposals at > future meetings and provide feedback, with the aim of converging > towards a cohesive set of proposals to present to the Committee at > large. > > Since this is a very broad area to explore, I believe the Study > Group is initially interested particularly in proposals that > provide infrastructure that compile-time reflection features can > be built on top of. This should become more clear when the > call for proposals is issued.
The call for proposals has now been posted. It can be found here: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3814.html It states that all reflection-related proposals will be considered, but the focus is on compile-time reflection, and gives a list of focus areas and representative use cases. Botond _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
