On 07/11/2012 06:55 PM, Eric Niebler wrote:
You're referring to this:
http://lists.boost.org/proto/2010/11/0304.php
I should have followed through! The code referenced there isn't
available anymore. I remember putting it on my TODO list to understand
the compile-time implications of it,
On 7/13/2012 6:37 AM, Mathias Gaunard wrote:
On 07/11/2012 06:55 PM, Eric Niebler wrote:
You're referring to this:
http://lists.boost.org/proto/2010/11/0304.php
I should have followed through! The code referenced there isn't
available anymore. I remember putting it on my TODO list to
On 7/11/2012 10:32 AM, Eric Niebler wrote:
f0(f1(f2(pack(_))...))
That's no so bad, actually. Now, the question is whether I can retrofit
this into proto-current without impacting compile times.
This is now implemented on boost trunk for proto-current. Seems to work
without a significant
On 07/10/2012 11:18 PM, Eric Niebler wrote:
I just committed to the proto-11 codebase a new transform called
_unpack. You use it like this:
_unpackf0(Tfx, f1(_)...)
Where Tfx represents any transform (primitive or otherwise) f0 is any
callable or object type, and f1(_) is an object or
On Tue, Jul 10, 2012 at 11:18 PM, Eric Niebler e...@boostpro.com wrote:
The _unpack transform is pretty general, allowing a lot of variation
within the pack expansion pattern. There can be any number of Tfx
transforms, and the wildcard can be arbitrarily nested. So these are all ok:
// just
On 7/11/2012 12:42 AM, Thomas Heller wrote:
On 07/10/2012 11:18 PM, Eric Niebler wrote:
I just committed to the proto-11 codebase a new transform called
_unpack. You use it like this:
_unpackf0(Tfx, f1(_)...)
Where Tfx represents any transform (primitive or otherwise) f0 is any
callable
