We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are a number of boost classes which can now be migrated over to the standard.
boost::bind
std::bind
boost::reference_wrapper
std::reference_wrapper
boost::any
std::any
boost::equality_comparable
std
boost::mpl::xxx
boost::remove_reference/remove_const/is_reference/etc...
boost::is_pod/is_integral/etc...
boost::enable_if
boost::begin/end/prev/next
boost::iteratorxxx
boost::mem_fn
std::mem_fn
boost::size
std::size
boost::range
boost::posix_time
std::chrono
boost::filesystem
std::filesystem
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There are a number of boost classes which can now be migrated over to the standard.
boost::bind
->std::bind
or lambdasboost::reference_wrapper
->std::reference_wrapper
boost::any
->std::any
boost::equality_comparable
and other concepts could be moved to theirstd
equivalentboost::mpl::xxx
have the potential to be migrated to similar constructs instd
boost::remove_reference/remove_const/is_reference/etc...
type traits could be migrated to theirstd
equivalentboost::is_pod/is_integral/etc...
havestd
equivalentsboost::enable_if
and other similar metaprogramming templates could be moved to theirstd
equivalentsboost::begin/end/prev/next
have equivalents instd
boost::iteratorxxx
types/helpers could be investigated to see if they can be replaced withstd
or range-based for loopsboost::mem_fn
->std::mem_fn
boost::size
->std::size
boost::range
related types and helpers could have equivalents in the standard based on the situationboost::posix_time
could potentially be migrated tostd::chrono
boost::filesystem
->std::filesystem
The text was updated successfully, but these errors were encountered: