fusion vector, spirit, phoenix actor and forwarding constructor

MM <[email protected]>
Newsgroups gmane.comp.parsers.spirit.general
Message-ID <CADsB1iAyo9aNOWeEEBez6R0GOYg=kw_ba2H0gtCQbt9cXE-Ddg@mail.gmail.com>
Hello,

In this user constructor for struct store in
/usr/include/boost/fusion/container/vector/vector.hpp:175:44

            template <typename U>
            BOOST_CONSTEXPR BOOST_FUSION_GPU_ENABLED
            store(U&& rhs
                , typename disable_if<is_same<typename pure<U>::type,
store>, detail::enabler_>::type = detail::enabler)
                : elem(std::forward<U>(rhs))
<= error is here
            {}

type of rhs is:
   const boost::phoenix::actor<boost::spirit::attribute<1> >&

the compiler meets this error:

no matching function for call to
‘boost::phoenix::actor<boost::spirit::attribute<1> >::actor(const
boost::spirit::attribute<1>&)’

candidates are the default ctor,
1) constexpr boost::phoenix::actor<boost::spirit::attribute<1> >::actor()

and the copy constructor
2) constexpr boost::phoenix::actor<boost::spirit::attribute<1>
>::actor(const boost::phoenix::actor<boost::spirit::attribute<1> >&)

This seems to be a problem only for >=c++11, also, it was ok with
1.58, but not now with develop.

I haven't managed to extract a small reproducible case yet, and but
i'll keep trying.

Thanks,

MM

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Spirit-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/spirit-general
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.