Ok, I haven't timed "typical use"; the only tests I've done in this respect is running the unit tests, but much of the time involved in that may well be taken by the test framework, as it uses mpl::for_each to iterate in two dimensions, taking a list of traits, and a list of types to test for each trait, which generates thousands of tests.
The unit tests take a rather long time to compile on Intel C++ (typically several minutes), but shorter on on MSVC, or g++.
that's a bit of a turn-off for me. I'm getting more and more annoyied by the fact that every time something *really cool* is discovered, it hits the compiler-time barrier. As I've said in posts to c.l.c++.m, maybe it's time for a new language... Best, John -- John Torjo -- john@torjo.com Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -- v1.4.0 - save_dlg - true binding of your data to UI controls! + easily add validation rules (win32gui/examples/smart_dlg)