boost::phoenix::bind issue in c++17.

Open
#101 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
devtools

Research direction

Start by reproducing the reported errors with Boost 1.73 and 1.77 under C++14 and C++17, using the diagnostics from include/boost/utility/result_of.hpp and include/boost/phoenix/core/detail/function_eval.hpp. Compare the relevant result_of and Phoenix behavior across versions; done means the compatibility cause is isolated and a focused regression case or documented resolution is identified.

Written by the indexing model from the issue text.

Description

Hi All,

I am facing these below issues when I upgrade from boost_1_73 and c++14 to boost_1_77 and c++17.
What will be the problem?
Error 1:
include/boost/utility/result_of.hpp:218:8: error: 'GB* (boost::intrusive_ptr::*)() const noexcept' is not a class, struct, or union type

Error 2:
include/boost/phoenix/core/detail/function_eval.hpp:119:21: error: no type named 'type' in 'struct boost::result_of<GB* (boost::intrusive_ptr::* const(boost::intrusive_ptr&))() const noexcept>'

Thank you.

Dominant language
C++
Stars
51
Forks
71
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boostorg/utility

All issues in boostorg/utility

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.