But I would prefer

phoneNumber ?: run { <see above> }

yeah here’s an example that motivated it:

return request
    ?.let { bridge.localServer.shouldInterceptRequest(it) }
    .orElse { Timber.d("Didn't intercept ${request?.url}") }

i wouldn’t say it’s the strongest case for it, but i’m having trouble recalling where i’ve wanted this before 🙂

basically i am pining for the else case in Swift’s if let

if let { .. } else { .. }

one of the few times i wish kotlin had something Swift does haha

Sorry I didn’t got what you would like to do 😄

You could create an extension function yourself

I just did 🙂 but I was wondering if there was something already there that I’d missed

?:

bothered me a few times as well, meaning I had to put parentheses to get the precedence right

thanks for discussion 🙂

👏 💯

Type is not matching, try succcess as CardReaderStatus

Hey! I have a list of a data class and I want to convert that into a map, which takes a property of the data class as key and the whole object as value

The call in the last line will not work obvously. Can I do something about it? A can guarantee that instanceA and instanceB have the same type. But I can't tell which one.

Thank you

Is it a bug?

why do inline classes have to be top-level ?

Is there a way to enforce a lambda to be

non-capturing

?

I just discovered that Kotlin doesn't support hexadecimal floating point literals! I'm surprised this didn't make it into the spec, considering it's supported by Java.

Hey guys, is there anyone else here using single activity pattern with a custom toolbar? I would like to get in touch with you. Please let me know

newb question, can you pass a parameter to a function conditionally?

say i call test(a, b) but i want b to only be passed if b is not null

hello how do i put my aar file of my android app into Unity

why having multiple signatures like this:

foo(bar: Type1)
foo(bar: Type2)
...

works but

foo(bar: Iterable<Type1>)
foo(bar: Iterable<Type2>)
...

doesn't?

because they're all iterables and it doesn't matter the type of each item?

because type erasure

to the JVM,

Iterable<A>

and

Iterable<B>

look exactly the same

so, basically, yes, what you said 🙂

I see, so the solution is to use

fun <T> foo(bar: Iterable<T>)

and handle it inside the function or?

yeah, that'll do it ^