Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add metafunction result_of::compose #75

Merged
merged 2 commits into from Apr 27, 2019

Conversation

@CromwellEnage
Copy link
Collaborator

commented Feb 19, 2019

Some Boost.Graph algorithms return one of their optional named function parameters. If the user doesn't specify the parameter, then the default return type must necessarily be different. This metafunction is needed to help facilitate computation of such a return type without resorting to decltype(), which not all compilers support.

Add metafunction result_of::compose
Some Boost.Graph algorithms return one of their optional named function parameters.  If the user doesn't specify the parameter, then the default return type must necessarily be different.  This metafunction is needed to help facilitate computation of such a return type without resorting to decltype(), which not all compilers support.

@CromwellEnage CromwellEnage merged commit dbf4dd2 into boostorg:develop Apr 27, 2019

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@CromwellEnage CromwellEnage deleted the CromwellEnage:feature_compose branch Apr 27, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.