Found this bizarre behaviour in 1.5.21: <https://p...
# random
d
Found this bizarre behaviour in 1.5.21: https://pl.kotl.in/v-YWrl1uT looks like it's already fixed in 1.5.30, but made me question my sanity when I first ran into it.. Trying to do an equality comparison on a primitive type that comes from a nullable interface is broken, and you can end up in a situation where you try to compare two bytes (in my example code) that have the same value, but the
==
comparison evaluates to
false
.
l
Can you edit your message to specify the issue a bit instead of kinda forcing all curious folks out there to click the link and have to check the code?
1
👍 2