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
How this API is currently, the user of it must have its own object, and the implementation of this API must create the object on its stack/global/whatever and then while returning copy constructor is called.
Why not to make it so the user jut give its object? virtual MessageBuffer *create(MessageBuffer *buf) = 0;
The text was updated successfully, but these errors were encountered:
amgross
changed the title
Why to use copy constructor if can write straight to the object
[QUESTION] Why to use copy constructor if can write straight to the object
Mar 18, 2024
erpc/erpc_c/infra/erpc_message_buffer.hpp
Line 364 in 2890823
How this API is currently, the user of it must have its own object, and the implementation of this API must create the object on its stack/global/whatever and then while returning copy constructor is called.
Why not to make it so the user jut give its object?
virtual MessageBuffer *create(MessageBuffer *buf) = 0;
The text was updated successfully, but these errors were encountered: