Memory usage on String/const *char in Particle cloud functions parameters?

[gusgonnet]

Hi all, I came across this post from Scruffr:

@ScruffR

// docs for Particle.function() state the callback needs to look like
int someFn(String args);
// but this works just the same
int someFn(const char* args);

from the memory consumption standpoint, is there a clear benefit to using the const *char option instead of the "default" String option?
Thanks!

[ScruffR]

The reason for that comment was to “relieve” the previous poster of the headache they feared with heaving to convert back and fro between String and const char*.

In that case it had nothing to do with memory management since the Particle.function() logic internally works with String either way.
However, when declaring the parameter as const char* the implementation of said function can use char* everywhere without ever needing to convert from String to const char* as that will be done implicitly when calling the function.

[gusgonnet]

@ScruffR

since the Particle.function() logic internally works with String either way

Thanks.
Does the above mean that both options are equivalent to memory usage (since Particle.function() is using String either way)? Thanks again.

[ScruffR]

Yup!
However, you can stay clear of String inside the function and thus avoid additional memory impact potentially incurred by temporary String variables therein.