<https://blog.simon-wirtz.de/the-power-of-gradle-k...

# feed

[s1m0nw1]

https://blog.simon-wirtz.de/the-power-of-gradle-kotlin-dsl/

[voddan]

The let function cried when you used it like this, but other than that, a very good post! Updated my build scrips 😉

[s1m0nw1]

What would you do instead of let?

[s1m0nw1]

Thanks for feedback!

[voddan]

I would make a local val - all the benefits, non of the confusion

[voddan]

My rule is that code should read as an english phrase. Example: list.let { print(it) }

[s1m0nw1]

Okay I see. That’s the problem when we have so many possibilities I guess. A local val is totally perfect too! I don’t think let is abused in the example though

[voddan]

Maybe my mistake is trying to find a healthy meaning in the names of functions like let and apply. I wonder what the guy that invented those thinks 😆

[s1m0nw1]

Yes I also have problems with the names sometimes, would be interesting to know why! Actually I would use with instead, but it would make the example worse

[ilya.gorbunov]

@voddan let is a "scope"-function and here it is used exactly to limit the scope of v variable for vertx dependencies only

[gildor]

maven { url = uri(it) } can be replaced with maven(it) or maven(url = it) if you want to be more explicit.

[voddan]

@ilya.gorbunov hm, why is it called let then? It could be called scope or something