You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the code uses boost::system to manage error handling. Within it, the majority of occurrences are of boost::system::error_code.
Dependencies on boost::system::error_code could be removed by using std::error_code, but that could probably result in a loss of compatibility with boost::asio. The loss of compatibility is not necessary (we can only know by testing), but the best way to remove boost::system dependency would be to remove boost::asio dependency along with it as well. However, removing boost::asio is not trivial. So try to find a way to remove boost::system dependency without breaking the code, and then test it to confirm that the code indeed works as expected. If this is not possible, then we will have to replace boost::asio by some standard library as well.
Currently, the code uses
boost::system
to manage error handling. Within it, the majority of occurrences are ofboost::system::error_code
.Dependencies on
boost::system::error_code
could be removed by usingstd::error_code
, but that could probably result in a loss of compatibility withboost::asio
. The loss of compatibility is not necessary (we can only know by testing), but the best way to removeboost::system
dependency would be to removeboost::asio
dependency along with it as well. However, removingboost::asio
is not trivial. So try to find a way to removeboost::system
dependency without breaking the code, and then test it to confirm that the code indeed works as expected. If this is not possible, then we will have to replaceboost::asio
by some standard library as well.This PR might be relevant for removing
boost::asio
: https://github.com/STEllAR-GROUP/hpx/pull/5158/filesThe text was updated successfully, but these errors were encountered: