Why do I get different boolean logic from "and" vs "&&"?
In the following unit-test, the 2nd test fails. But the only difference is that one uses and for its boolean operator and the other uses &&.
My understanding is that those two operators are logically the same (but that and does not short-circuit).
import org.junit.Test
import kotlin.test.assertFalse
import kotlin.test.assertTrue
class BooleanAndComparisonTest {
data class CustomerProfile(val deleted: Boolean, val mobileVerified: Boolean)
@Test
fun testUsingDoubleAmpersand() {...