any working code example maybe? :wink:

# announcements

[arekolek]

any working code example maybe? 😉

[Shawn]

lol sure, if you’d really like

[Shawn]

https://github.com/shawnrc/kemohno/blob/develop/src/main/kotlin/me/shawnrc/kemohno/SlackClient.kt#L47-L85

[Shawn]

in the call to <http://khttp.async.post|khttp.async.post>() there’s an optional onResponse param that takes Response.() -> Unit

[Shawn]

oh, guh, actually, this version of the code doesn’t use .let

[Shawn]

initially I was under the impression that JSONObject.getString() with a nonexistent key would return null, so for a bit there, the last line was a ?.let { log }

[arekolek]

😄

[arekolek]

maybe you can contrive a really simple example?

[arekolek]

like 2-3 lines of code

[Shawn]

hm, might take me a sec to match the exact weirdness of the original situation

[Shawn]

here, though it’s 11 lines

[Shawn]

interface Foo {
  val string: String?
  fun frobnicate(block: Foo.() -> Unit)
}

fun consume(foo: Foo) {
  val baz = { lad: Foo ->
    lad.string?.let(::println)
  }
  foo.frobnicate(baz)
}

[Shawn]

that yields a compiler error

[Shawn]

setting val baz: (Foo) -> Unit fixes it

[Shawn]

or tacking on ?: Unit onto the let line

[arekolek]

yeah, nice example, that makes it clear 🙂

[arekolek]

I also think explicit type would be best here

[arekolek]

how about something like this:

fun consume(foo: Foo) {
    val baz: Foo.() -> Unit = {
        string?.let(::println)
    }
    foo.frobnicate(baz)
}

[arekolek]

although that might apply only when the lambda is with receiver

[gildor]

+1 for explicit type

[gildor]

It’s also good for such lambda declarations with other types

[gildor]

otherwise it’s to easy implicitly change type of variable with lambda