It means exactly what it says.
A function that promises to return a value does just end without ever returning the value.
Obviously the programmer “forgot” in at least one code path the required return statement.
This may have built in the past as the compiler was more lenient about this issue.
But, since such an error can cause unexpected behaviour (including SOS panic crashes) the rule to demand a return statement at compile time was enforced.
Have there been any updates on this issue. I assume that they used the following gitgub repository since there are not that many out there. Would it be possible to add it myself? I am still having issues with the sps30.h library.
I am one of the members that add this library for particle. In stead of returning a variable, these functions edit the proveded arrays and places the values in the array. Not sure why you are getting verify errors. I just compiled in the project we wrote this for and in a new test project and both came back successful.
That might be so, but when a function promises to return a value it has to do so too.
If you don’t want to return anything you should make it a void function (and not a void*).
But the return value doesn’t always have to be the same as the object of its action but a mere “status report” - as many functions do.
Which device OS version did you target for that test?