(This is

initOnce

property delegate)

#tornadofx uses a custom implementation, so it must be useful

What is the difference between <T> and <T : Any> declaration for kotlin generic types?

that's to say that T is non-nullable for

<T : Any>

, but can be for

<T>

Is there a reason for the inconsistent naming of

measureNanoTime

and

measureTimeMillis

?

Most likely to be consistent with

System.currentTimeMillis()

and

System.nanoTime()

We're evaluating naming options for a function that is similar to

apply

but operates on

it

instead of

this

inside it's lambda. Our two shortlisted candidates are

btw

and

also

. The function is designated to be used in a situation when you need to perform a side-effect on some value, before passing it somewhere else. For example: 1️⃣

val result = getSomeValue().btw { do_something_with(it) }

2️⃣

val result = getSomeValue().also { do_something_with(it) }

What do you think guys, which of these names fits better for K?

.then

?

i was going to say

then

,

andThen

, or just

and

btw

is terrible, btw.

thenDo

?

The key being that

do

pushes the 'effect occurs here' side

Speaking of effects…

affect

?

Also it will teach people the difference between “effect” and “affect” 🧌

modify

?

I could see arguments for

map

map

to me doesn’t perform side effects

oh, yeah, agreed 100%. I take back my statement.

I thought we were getting the result of the

do_something_with(it)

as the

result

but I have now read more carefully

Same vein as `do`:

execute

streams have

onEach

for side-effects and takes a

(T) -> Unit

. Maybe

on

?

We'd like not to occupy too short and generic names as it might hurt various DSLs

Thus no

on

and

then

. And

and

is a bitwise operator

Obviously the solution is to rename the bitwise operators

Yeah the old-school arrows look much better for bitwise operations.

is there a KEEP or something official under which we can discuss naming?

@jw https://youtrack.jetbrains.com/issue/KT-6903#comment=27-1276131