mirror of
https://github.com/zeromq/libzmq.git
synced 2025-10-30 13:47:13 +01:00
Remove early return on terminated state
Code as stands breaks shutdown process. It was a bugfix by Arthur to a bad line which was testing for an impossible state - but afaics we do actually want to flush in those states. It is possible I am wrong on that though - if there are any shutdown issues introduced aroudn this commit I would suggest further investigation around this flushing behavior.
This commit is contained in:
@@ -189,10 +189,6 @@ void zmq::pipe_t::rollback ()
|
|||||||
|
|
||||||
void zmq::pipe_t::flush ()
|
void zmq::pipe_t::flush ()
|
||||||
{
|
{
|
||||||
// If terminate() was already called do nothing.
|
|
||||||
if (state == terminated || state == double_terminated)
|
|
||||||
return;
|
|
||||||
|
|
||||||
// The peer does not exist anymore at this point.
|
// The peer does not exist anymore at this point.
|
||||||
if (state == terminating)
|
if (state == terminating)
|
||||||
return;
|
return;
|
||||||
|
|||||||
Reference in New Issue
Block a user