Is there something that's like a combo of `use` an...

# announcements

[mathew murphy]

Is there something that's like a combo of use and with?

[Shawn]

What do you mean exactly by “combo”

[mathew murphy]

e.g.

db.getConnection().useWith {
  prepareStatement(...).useWith {
    setString(1, "Hello sailor")
    execute()
  }
}

[Shawn]

T.run {} has a signature of (T.() -> R) -> R, maybe that’s what you want?

[Shawn]

I’m assuming prepareStatement is a method on the connection from getConnection?

[Shawn]

you might just want apply {} if you’re just returning Unit

[bezrukov]

He also want connection to be closed after run or apply

[Shawn]

oh, whoops, forgot about use closing automatically

[mathew murphy]

Sorry, this is JDBC, should have mentioned.

[mathew murphy]

So yes, AutoClose is important.

[Mike]

Is it really that much more to stick with use and it?

Or give the parameter a meaningful name to eliminate ambiguity in usage?

Sometimes less concision leads to higher readability.

[mathew murphy]

Sure, I've gone ahead and used use. I was just wondering if there was an even shorter way to do it.

[mathew murphy]

If anything I feel like Kotlin offers too many convenient shortcuts to eliminating code, but I'm coming to it from Go... (and Java)

[Mike]

I'd agree that sometimes there are too many ways to do something. There are docs that provide some conventions, mostly around let/apply/also/run/with that seem to be consistent, but definitely other areas where it's vague.

[mathew murphy]

Docs in general are a bit skimpy, getting OkHttp and Moshi working was frustrating, partly because even when libraries are written in Kotlin it often seems to be the case that they're documented on the assumption that you're calling them from Java.

[mathew murphy]

Also, how coroutines relate to threads and suspend functions relate to blocking calls could use some careful explanation.

[mathew murphy]

But, I'm doing the same work with massively less code in the end, and that's a good thing.

[gildor]

Do you have any example why do you need this?
Why not just:
e.g.

db.getConnection().use { connection ->
  connection.prepareStatement(...).use { statement ->
    statement.setString(1, "Hello sailor")
    statement.execute()
  }
}

[gildor]

I mean multiple nested context are not something pleasant to use imp

[gildor]

But it's easy to implement this useWith extension