|
Boost : |
From: Frank Mori Hess (frank.hess_at_[hidden])
Date: 2008-05-15 09:15:24
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've just noticed that neither Anthony's or Braddock's future libraries seem
to support construction of a future directly from a value, like
future<int> fut_int(5);
Adding such a constructor gives support for implicit conversion of a value of
type T to a future<T>. So a function which takes futures as arguments can
also seamlessly accept values:
future<void> my_func(future<int> f1, future<int> f2);
my_func(fut_int, 3);
This is important for the usability of poet::active_function, which takes all
parameters as futures.
- --
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFILDds5vihyNWuA4URAguzAJwIFdVharrD6w1QMq0R7H6NVV8TJgCfQ1hw
MeYEoiqA5mOy0wY52n/tHE0=
=6tTp
-----END PGP SIGNATURE-----
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk