QUESTION: Why to ignore all the socket closing errors in beast.cpp?

[Pilipets]

Speaking of the code snippet beast.cpp,

// Gracefully close the socket
boost::beast::error_code ec;
stream.shutdown(ec);

what is the reason for ignoring the socket error closing error?

According to the htt_client_sync_example from the boost::beast developers, that error is supposed to be treated as such.
While I agree, the error there isn't important according to the boostorg/beast#824, explicit comment pointing that out might be useful.