The if would be here

# announcements

[HaSH]

The if would be here

[dewildte]

Have you tried if (!object.string.equals("string")) { code }?

[karelpeeters]

How do you know the strings actually match?

[HaSH]

@dewildte I hadn't, I just tried now and it appears .equals() is behaving as expected. I honestly thought == and .equals would work the same for String. Thanks for pointing me towards a solution.

[karelpeeters]

They are the same!

[karelpeeters]

(in Kotlin at least, not in Java)

[HaSH]

@karelpeeters I put a few breakpoints in and manually evaluated

[HaSH]

@karelpeeters haha. dun dun dun...plot thickens

[HaSH]

(No idea why one works and not the other)

[karelpeeters]

Can you take a look at the generated bytecode to see what == compiles down in your code?

[karelpeeters]

How did you test equality with the debugger?

[karelpeeters]

Are you sure you didn't accidentally do ===?

[dewildte]

From my (limited) understanding != and !string.equals(...) are not the same.

[HaSH]

@karelpeeters I'm not sure how to examine the bytecode, is it something I can easily see?

[karelpeeters]

Tools > Kotlin > Show generated bytecode

[karelpeeters]

(and then press decompile to get the Java version of the code)

[dewildte]

CTRL+A "show kotlin byte code"

[karelpeeters]

@dewildte Well except for some nullability stuff != and !.equals are exactly the same.

[dewildte]

Are they structural or referential?

[HaSH]

To debug in AS(this is a android project) I put a break point in AFTER object is instantiated and also on the same line as the if statement. If you hover over the var in AS while at a stop point you can look at the underlying data

[dewildte]

=== is referential is it not?

[HaSH]

So I would know the value of object.string before the if code ran

[karelpeeters]

Yes, K === is reference equality, so ☕ ==, and K == is structural so ☕ .equals.

[dewildte]

Java will give you a warning when trying to compare strings with == and !=.
Warning says to use .equals(...)
That's why I suggested using it.

[HaSH]

That show bytecode feature is cool. but I don't know how to read bytecode lol

[HaSH]

Give me a sec to look

[karelpeeters]

That's what the compile button is for simple smile

[karelpeeters]

@dewildte But this is Kotlin!

[dewildte]

Wibbly wobbly Kotlin javaey stuff.

[dewildte]

lol

[dewildte]

Anyway .equals(...) works for John.

[dewildte]

I have contributed my piece. lol

[HaSH]

Seems they call different things in bytecode?

[dewildte]

AHA!

[HaSH]

The .equals:

[HaSH]

INVOKEVIRTUAL java/lang/String.equals (Ljava/lang/Object;)Z

[dewildte]

The truth is revealed!

[HaSH]

The ==:
INVOKESTATIC kotlin/jvm/internal/Intrinsics.areEqual (Ljava/lang/Object;Ljava/lang/Object;)Z

[HaSH]

Or am I reading things wrong haha

[karelpeeters]

And you'll never guess what the source of that function is like...

[HaSH]

lol

[karelpeeters]

public static boolean areEqual(Object first, Object second) {
    return first == null ? second == null : first.equals(second);
}

[HaSH]

haha

[dewildte]

Wow

[karelpeeters]

So there must be something else going on.

[dewildte]

That is casting them as Object, but that should not matter.

[dewildte]

I swear string equality is tricky.

[HaSH]

I'm far from a "real" programmer, but nothing jumps out at me as to why this is happening.

[karelpeeters]

Would it be possible to create a minimal example we can run?

[dewildte]

Dude you just compiled byte code.
How much more "real programmer" do you need?

[HaSH]

A job

[HaSH]

😉

[dewildte]

Lol!!!!

[HaSH]

Let me see how much code is related to this

[dewildte]

I am laughing so hard right now

[HaSH]

👍

[HaSH]

I think I can get an example made up in a couple mins, will post if I can recreate

[dewildte]

Cool

[HaSH]

Yea, of course... I can't recreate in a separate project. Figures...

[karelpeeters]

It could be a debugger bug as well.

[HaSH]

Yea, I can't reproduce. Figures! haha. Thanks for the help!