mirror of
https://github.com/boostorg/fusion.git
synced 2025-07-29 20:17:32 +02:00
merge from trunk
[SVN r42226]
This commit is contained in:
@ -9,8 +9,17 @@
|
||||
|
||||
This section summarizes significant changes to the Fusion library.
|
||||
|
||||
* Sep 27, 2006: Added `boost::tuple` support.
|
||||
* Nov 17, 2006: Added `boost::variant` support.
|
||||
* Feb 15, 2007: Added functional module.
|
||||
* Sep 27, 2006: Added `boost::tuple` support. (Joel de Guzman)
|
||||
* Nov 17, 2006: Added `boost::variant` support. (Joel de Guzman)
|
||||
* Feb 15, 2007: Added functional module. (Tobias Schwinger)
|
||||
* APRIL 2, 2007: Added struct adapter. (Joel de Guzman)
|
||||
* May 8, 2007: Added associative struct adapter. (Dan Marsden)
|
||||
* Dec 20, 2007: Removed `boost::variant` support. After thorough
|
||||
investigation, I think now that the move to make variant a
|
||||
fusion sequence is rather quirky. A variant will always
|
||||
have a size==1 regardless of the number of types it can contain
|
||||
and there's no way to know at compile time what it contains.
|
||||
Iterating over its types is simply wrong. All these imply that
|
||||
the variant is *not* a fusion sequence. (Joel de Guzman)
|
||||
|
||||
[endsect]
|
||||
|
Reference in New Issue
Block a user