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
They are very close, but not the same. execute() waits for "OK", send() waits for ">". I thought about combining them into one func, but that would cause problems if a sending process see's the OK from another process that's executing a cmd, like creating another socket.
Maybe there is a way to DRY the duplicated parts of send() and execute()?
I thought about combining them into one func, but that would cause problems if a sending process see's the OK from another process that's executing a cmd, like creating another socket.
[Caffeine kicking in]...scratch that thought...the two competing processes are mutual ex due to d.Lock().
But I still like being explicit about expected result after an execute() cmd vs. a send() cmd. Maybe the code just needs a // comment covering this?
The "execute" and "send" methods for this driver have the exact same implementation
drivers/comboat/comboat.go
Line 142 in 06dd60f
The text was updated successfully, but these errors were encountered: