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
.pio/libdeps/esp32dev/PubSubClient_imroy_/src/MQTT.cpp: In member function 'virtual MQTT::message_type MQTT::Publish::response_type() const':
.pio/libdeps/esp32dev/PubSubClient_imroy_/src/MQTT.cpp:602:3: warning: control reaches end of non-void function [-Wreturn-type]
}
^
The text was updated successfully, but these errors were encountered:
Ditto for me on ESP-8266 , the code worked originally so I am assume PIO (especially compiler: Core 6.1.4 Home 3.4.3) updates make this more stringent? Is this as straight forward as rewriting the function to read?:
message_type Publish::response_type(void) const {
switch (qos()) {
case 1:
return PUBACK;
case 2:
return PUBREC;
default:
return None;
}
}
Obviously compiles etc., but any unwanted side effects? I note the case indices do not relate to the enum order in any event, since that reads:
Building for Esp32 appears this Warning:
The text was updated successfully, but these errors were encountered: