Weird == vs .equals() behavior

I would think "duck typing" would allow the use of == or != to apply to string types too.

In conditionals, I have to use varName1.equals(varName2) for some types. If I accidentally use "==" in those situations, it seems at times I don't get an error, it just silently does the wrong thing.

Just a suggestion that the language gurus consider adapting the == parsing to handle all types.

Brandon.ConnectIQ over 7 years ago

There are a few inconsistencies with the behavior of '==' and '.equals()' that have come up in previous conversations. Here's an example:

https://forums.garmin.com/forum/developers/connect-iq/132304-equals-on-arrays-not-working?351763-equals()-on-Arrays-not-working=

We also have a documentation ticket open to better define cases where one should be used over the other. The general idea is one should be used to see if two things reference the same object, and the other compares the value of two objects. It's unlikely that we'll change the behavior of these, but we definitely need to explain their use.