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
I can't see the benefit of the grouping brought by "can_read_multiple_v" in read.hpp. Ultimately, everything is forwarded and called sequentially via "read_single_t". Why not simplify the process and directly call “read_single_t” for each argument of the read interface?
The text was updated successfully, but these errors were encountered:
Good question. I'm not sure what happened here. At one point we use to call sd_bus_message_read with multiple values and it seems like that got lost at some point in some refactoring. You're right that right now it seems like we do tons of template processing for no reason. This is probably an opportunity for performance improvement to get us back to doing multiple reads in one shot.
I can't see the benefit of the grouping brought by "can_read_multiple_v" in read.hpp. Ultimately, everything is forwarded and called sequentially via "read_single_t". Why not simplify the process and directly call “read_single_t” for each argument of the read interface?
The text was updated successfully, but these errors were encountered: