Merge 'develop' changes #77
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
CromwellEnage
commented
Apr 27, 2019
CromwellEnage
commented
- Upgraded keyword generation macro BOOST_PARAMETER_TEMPLATE_KEYWORD (PR#15).
- Moved keyword generation macro BOOST_PARAMETER_NESTED_KEYWORD from Boost.Accumulators to this library (PR#28).
- Added support for std::reference_wrapper<> and std::ref() (PR#16).
- Added support for passing functions as arguments to Boost.Parameter-enabled functions (PR#17).
- Moved boost::parameter::required, boost::parameter::optional, and boost::parameter::deduced metafunction definitions to their own header files in directory boost/parameter (PR#18).
- Added support for Boost.Parameter-enabled function call operators (PR#20).
- Added support for parameter category qualifiers "forward”, "consume”, and "move_from" (current qualifiers are "in", "out", and "in_out") (PR#21) (PR#23) based on http://www.modernescpp.com/index.php/c-core-guidelines-how-to-pass-function-parameters. Added new usage syntax BOOST_PARAMETER_NAME((object-name), namespace-name) qualifier(tag-name)) and BOOST_PARAMETER_NAME(qualifier(name)). (Existing code that uses qualifiers directly and correctly with BOOST_PARAMETER_FUNCTION and other code generation macros should remain unaffected for now, so no breaking changes.) The reason for the change in usage is to enable applying of parameter category constraints to Boost.Parameter-enabled functions and constructors invoked through argument composition. (Otherwise, it is currently possible to use argument composition to bypass parameter category constraints applied in BOOST_PARAMETER_FUNCTION et. al.)
- Added support for perfect forwarding (PR#23) (PR#26), so that parameter::parameters::operator() can accept non-const rvalues. As a positive side effect, Boost.Parameter-enabled functions and constructors are no longer bound by BOOST_PARAMETER_MAX_ARITY on compilers that support perfect forwarding. User code can now check for this support by detecting the configuration macro BOOST_PARAMETER_HAS_PERFECT_FORWARDING, or manually turn off this support by defining the configuration macro BOOST_PARAMETER_DISABLE_PERFECT_FORWARDING.
- Added metafunctions boost::parameter::is_argument_pack (PR#27), boost::parameter::are_tagged_arguments (PR#52), and boost::parameter::result_of::compose (PR#75).
- Added variadic function template boost::parameter::compose() which takes in named arguments and returns them in an argument pack (PR#52). For compilers that do not support perfect forwarding, the configuration macro BOOST_PARAMETER_COMPOSE_MAX_ARITY determines the maximum number of arguments that boost::parameter::compose() can take in (PR#61).
- Added code generation macros BOOST_PARAMETER_BASIC_FUNCTION_CALL_OPERATOR, BOOST_PARAMETER_BASIC_CONST_FUNCTION_CALL_OPERATOR, BOOST_PARAMETER_NO_SPEC_FUNCTION, BOOST_PARAMETER_NO_SPEC_MEMBER_FUNCTION, BOOST_PARAMETER_NO_SPEC_CONST_MEMBER_FUNCTION, BOOST_PARAMETER_NO_SPEC_FUNCTION_CALL_OPERATOR, BOOST_PARAMETER_NO_SPEC_CONST_FUNCTION_CALL_OPERATOR, BOOST_PARAMETER_NO_SPEC_CONSTRUCTOR, and BOOST_PARAMETER_NO_SPEC_NO_BASE_CONSTRUCTOR (PR#52).
- Added support for Boost.MP11 (PR#47) (PR#66) (PR#70). User code can now check for this support by detecting the configuration macro BOOST_PARAMETER_CAN_USE_MP11, or manually turn off this support by defining the configuration macro BOOST_PARAMETER_DISABLE_MP11_USAGE.
- Improved support for parameter-dependent return types via SFINAE (PR#73).
Keyword templates generated by BOOST_PARAMETER_TEMPLATE_KEYWORD can now accept function types.
Change run statement to compile statement.
Upgrade BOOST_PARAMETER_TEMPLATE_KEYWORD
Merge with boostorg/parameter
Add support for std::reference_wrapper<> and std::ref().
Add support for passing functions as arguments to Boost.Parameter-enabled functions.
Upgrade boost::parameter::aux::unwrap_cv_reference
Change compile statement to run statement for compose.cpp
….cpp to tagged_argument.hpp Test the behavior of MSVC-11.0.
…/compose.cpp to tagged_argument.hpp"
Merge with boostorg/parameter
test/compose.cpp: Change workarounds from boost::function to std::function since msvc-11.0 reports having a C++11-compliant <functional> header. Add LIBS_PARAMETER_TEST_RUN_FAILURE configuration macro to facilitate run-fail testing. test/Jamfile.v2: Replaced deprecated test-suite statement with alias statements. Added run-fail test case under its own alias statement. appveyor.yml: Add mingw compiler configurations to the test matrix. Update msvc-11.0 configuration to also execute the run-fail test. travis.yml: Ensure that only the standard tests are run, not the run-fail test.
…gument Upgrade boost::parameter::aux::tagged_argument
<boost/parameter/aux_/arg_list.hpp>: Move forward declarations to their own header files. <boost/parameter/aux_/tagged_argument.hpp>: * Move boost::parameter::aux::tagged_argument_base, boost::parameter::aux::is_tagged_argument_aux, and boost::parameter::aux::is_tagged_argument to <boost/parameter/aux_/is_tagged_argument.hpp> * Remove unnecessary forward declarations. <boost/parameter/parameters.hpp>: * Move support metafunction definitions to their own header files in directory boost/parameter/aux_/pack. * Move support macro definitions to <boost/parameter/aux_/preprocessor/no_perfect_forwarding_begin.hpp> and their corresponding #undef statements to <boost/parameter/aux_/preprocessor/no_perfect_forwarding_end.hpp>. <boost/parameter/aux_/overloads.hpp> works at the preprocessor level, so move to <boost/parameter/aux_/preprocessor/overloads.hpp>. <boost/parameter/preprocessor.hpp>: * Move voidstar type definition to <boost/parameter/aux_/void.hpp>. * Move support metafunctions to their own header files in directory boost/parameter/aux_/pp_impl. * Move support macros to header files in directory boost/parameter/aux_/preprocessor/impl.
<boost/parameter/name.hpp>: * Move support metafunction definitions and BOOST_PARAMETER_TAG_PLACEHOLDER_TYPE macro definition to <boost/parameter/aux_/name.hpp>. * Move BOOST_PARAMETER_IS_BINARY macro definition to <boost/parameter/aux_/preprocessor/is_binary.hpp>. * Use BOOST_PARAMETER_TAG_PLACEHOLDER_TYPE macro.
Add #include statement for forward declaration.
Document that boost::parameter::required, boost::parameter::optional, and boost::parameter::deduced are defined in their own header files, which are in turn #included by <boost/parameter/parameters.hpp>.
Restructure code
* Add code generation macros BOOST_PARAMETER_FUNCTION_CALL_OPERATOR and BOOST_PARAMETER_CONST_FUNCTION_CALL_OPERATOR to <boost/parameter/preprocessor.hpp>. * Also, add documentation for BOOST_PARAMETER_CONST_MEMBER_FUNCTION, BOOST_PARAMETER_BASIC_FUNCTION, BOOST_PARAMETER_BASIC_MEMBER_FUNCTION, and BOOST_PARAMETER_BASIC_CONST_MEMBER_FUNCTION.
Support Boost.Parameter-enabled function call operators.
Add parameter category qualifier "forward" (current qualifiers are "in", "out", and "in_out") based on http://www.modernescpp.com/index.php/c-core-guidelines-how-to-pass-function-parameters. Add new usage syntax BOOST_PARAMETER_NAME((object-name), namespace-name) qualifier(tag-name)) and BOOST_PARAMETER_NAME(qualifier(name)). (Existing code that uses qualifiers directly and correctly with BOOST_PARAMETER_FUNCTION and other code generation macros should remain unaffected for now, so no breaking changes.) The reason for the change in usage is to enable applying of parameter category constraints to Boost.Parameter-enabled functions and constructors invoked through argument composition. (Otherwise, it is currently possible to use argument composition to bypass parameter category constraints applied in BOOST_PARAMETER_FUNCTION et. al.) See "test/compose.cpp" for example usage.
Support additional parameter categories
<boost/parameter/parameters.hpp>: * Add preprocessor conditional statement to prevent generation of ill-formed function call operator overloads. "test/maybe.cpp" "test/singular.cpp" "test/tutorial.cpp" "test/sfinae.cpp" "test/earwicker.cpp" * Replace BOOST_PARAMETER_KEYWORD statements with BOOST_PARAMETER_NAME statements. "test/optional_deduced_sfinae.cpp" "test/normalized_argument_types.cpp" "test/literate/*.cpp" * Use Boost.Core.LightweightTest where int main() is available. * Replace assert statements with BOOST_TEST_EQ statements. "test/basics.hpp" * Remove preprocessor statements regarding borland, gcc-2, and msvc workarounds. "test/ntp.cpp" "test/sfinae.cpp" "test/earwicker.cpp" "test/normalized_argument_types.cpp" "test/basics.hpp" * Add preprocessor conditional statement to #error out if BOOST_PARAMETER_MAX_ARITY is set to an insufficient value. "test/basics.cpp" "test/deduced.cpp" "test/macros.cpp" "test/preprocessor.cpp" "test/preprocessor_deduced.cpp" * Replace S and char const* expressions with boost::container::string expressions. * Uncomment any code that fails to compile, but add preprocessor conditional statement so that test suites can incorporate compile-fail statements regarding the code in question. * Ensure that int main() returns boost::process_errors(). "test/literate/deduced-template-parameters0.cpp": "test/literate/exercising-the-code-so-far0.cpp": * Enclose BOOST_MPL_ASSERT statements within MPL_TEST_CASE block. "test/literate/defining-the-keywords1.cpp": * Add graphs::tag::graph::qualifier type definition because perfect forwarding code will check for it. * Replace deprecated keyword::get() invocation with keyword::instance invocation. test/Jamfile.v2: * Add modifier <define>BOOST_PARAMETER_MAX_ARITY=# to run, run-fail, compile, and compile-fail statements to conserve compiler memory usage on GitHub's side. * Add modifier <preserve-target-tests>off to run and run-fail statements to conserve executable space on GitHub's side. * Separate bpl-test statement into its own target, parameter_python_test, which fails on xcode8.3 as well as on mingw and msvc compilers with address-model=64. * The next commit (which will implement perfect forwarding) will subsume test/literate/Jamfile.v2 into this file. Strangely enough, attempting to do so now will result in compiler errors. .travis.yml: * Add g++-4.7, g++-4.8, g++-4.9, clang++-3.5, clang++-3.6, clang++-3.7, clang++-3.8, clang++-3.9, clang++-4.0, xcode7.3, and xcode8.3 compiler configurations. * Split compiler configurations by available CXXSTD values. (This will keep the job times within limits for the next commit.) * Ensure that the xcode8.3 compiler configurations exclude parameter_python_test from the test suite. appveyor.yml: * Add compiler configurations that support address-model=64 to the test matrix. * Ensure that the new configurations exclude parameter_python_test from the test suite.
Replace with std::string.
These are breaking changes to PR #66. * Remove are_tagged_arguments_mp11 and is_argument_pack_mp11. They were reviewed as redundant. * Remove MP11 support for ArgumentPack models for now. (This feature relied on templates that were not supposed to be specialized.)
Modify MP11 support
Argument packs qualify as Boost.MP11-style maps as well as MPL sequences. These maps store the keyword tag types as their keys.
Reinstate MP11 support for ArgumentPacks
Eliminate warnings regarding undefined inline functions
…erated by preprocessor macros The code generation macros are supposed to support parameter-dependent return types, but it turns out that they currently don't really do that. This commit fixes the issue.
…_return_types Improve support for parameter-dependent return types of functions generated by preprocessor macros
In my GitHub fork of Boost.Graph, I've been upgrading some algorithms to use BOOST_PARAMETER_FUNCTION, but MinGW with GCC 5.3.0 has been running out of heap space on some of the affected tests. The goal of this commit is to eliminate these occurrences.
The Boost regression test matrix shows failures with GCC 5 due to running out of heap space. The goal of this commit is to eliminate these failures.
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.
Set BOOST_PARAMETER_COMPOSE_MAX_ARITY to 20 for GCC 5-
Add metafunction result_of::compose
|
Looks like you've been hit by the Boost.Build changes mentioned on the list - don't ask me to explain it though! |
|
I think I forgot to update the AppVeyor script by changing Visual Studio 2013 to Visual Studio 2015. I'll see if doing so works. |
Update appveyor.yml to handle changes in Boost.Build
Add missing reference documentation for lazy_value_type
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.