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, azmq::message move ctor/assignment implements the equivalent of zmq_msg_move(). This is not error prone against future changes in ZMQ. I propose to simply call zmq_msg_move() instead.
Btw, current implementation of move assignment has leak: existing message is not closed before assigning.
The text was updated successfully, but these errors were encountered:
Currently,
azmq::message
move ctor/assignment implements the equivalent ofzmq_msg_move()
. This is not error prone against future changes in ZMQ. I propose to simply callzmq_msg_move()
instead.Btw, current implementation of move assignment has leak: existing message is not closed before assigning.
The text was updated successfully, but these errors were encountered: