set the channel description: Suggestions, Feedback, Comments. All welcome

Hi, enjoying the podcast. For this particular one the soundcloud download button is missing, any way to fix that? http://talkingkotlin.com/Writing-A-Clojure-IDE-in-Kotlin-with-colin-fleming/

I think the feed for today is broken.

Anyone else having an issue?

Feed? Or just latest track?

Latest track

The one with @Mark

I’d put it through auphonic but seems it messed up for some folks. I re-uploaded again and it should be resolved.

Thanks !

Does Kotlin ever get used for ml?

Hi @hhariri ! I just wanted to take a moment and say that I’m really enjoying the podcast. I’m new to Kotlin, and hearing stories of other developers’ experiences has really motivated me to learn more. Thank you.

@roman.belov in the Data Science podcast https://talkingkotlin.com/catching-up-with-data-science-at-jetbrains/ you talk about “type providers” I found the concept fascinating but I wasn’t able to find any information about Kotlin implementation. Do you have pointers I can look at?

@hhariri , with the new show format, are you stopping the podcast feed and just using YouTube now?

Would it be possible to enhance the RSS feed? (https://talkingkotlin.com/feed) Like including the description, linking the audio file and including a youtube link

I'm trying to learn coroutines and came across this bit of documentation about dispatchers, why should unconfined not be used? It seems like it should be the best default dispatcher, whichever thread is free executes the next ready task 🤔

edit: moved to different channel

Not sure which channel this should go in, so let me know if it should go somewhere else: Given this infix function, that implies

this

is

T

if it returns true

@OptIn(ExperimentalContracts::class)
inline infix fun <reified T : PsiElement> PsiElement.matches(pattern: PsiElementPattern.Capture<T>): Boolean {
    contract { returns(true) implies (this@matches is T) }
    return pattern.accepts(this)
}

the contract doesn’t work if calling it using infix syntax: nono

inline fun <reified T : PsiElement, Y> PsiElement.doIfMatches(
    pattern: PsiElementPattern.Capture<T>,
    block: (T) -> Y
): Y? =
    if (this matches pattern) { // <-- infix call
        block(this) // <-- "[TYPE_MISMATCH] Type mismatch. Required: T Found: PsiElement"
    } else {
        null
    }

This works nod

inline fun <reified T : PsiElement, Y> PsiElement.doIfMatches(
    pattern: PsiElementPattern.Capture<T>,
    block: (T) -> Y
): Y? =
    if (this.matches(pattern)) { // <-- none infix call
        block(this) // <-- "Smart cast to T (for null call)" (appears twice for some reason)
    } else {
        null
    }

Any idea what’s going on here? is this an issue with contracts (being experimental and all)?

I'm just beginning to learn about classes in the compose course, and with the information I have, I'm confused about secondary constructors. I think I understand them correctly to be an alternative to the primary constructor as opposed to supplementing or adding to it after it would be run. They're invoked not by name, but based on the parameters you supply when instantiating an object. What I don't get is why, in the body of the class this is necessary.

:this (primary constructor paramaters)

Is there some future benefit to this method I'll uncover as I learn more? Because right now it seems unnecessarily redundant to supply the parameters from a call to the primary when they could just be sent directly to the appropriate secondary. Or maybe I'm wrong? Maybe both primary and secondaries DO get called together, separating concerns for safety? So that vital data is always reliably built with the primary, and then added onto by the secondaries if possible?

set the channel topic: 🎤 For discussions related to the Talking Kotlin podcast

I realize that this channel hasn't been very active, but hopefully we do have some listeners in here. I'll try posting new episodes as they come out, to see if there's any interest in discussing the topics here! Starting with our latest episode, where @Sebastian Aigner and @Alexander Sysoev chatted about #C072YJ3Q91V: