it looks odd either in java or in kotlin, if i move it into a subpackage it looks odd in java (import ....varints.VarInts) if I dont it looks odd in kotlin (import ....readVarInt)

I either get double grouping in java, or no grouping in kotlin (when looking at the code from the outside)

not sure what kind of grouping do you mean, isn’t a file good enough grouping?

I like the grouping to be visible in the imports, especially if i have more such objects

I don’t really see how object is different form package here, either form Kotlin or Java.

But I admit I don’t do a lot of K2J interop myself, so may be missing some use case specifics.

i get to use at.yawk....varints.VarInts.readVarInt in java which is an odd api structure

but either way, im gonna think about which is more important to me, the grouping or auto import. good to know theres a ticket for it. thanks for the help

but if

VarInts

is object or a subpackage file, it looks the same, no?

in kotlin, the imports are different, and not grouped

with top-level functions I'm polluting the namespace of the package, if I use a subpackage that's an odd api from javas view

You don’t really polluting the namespace in Kotlin, because these functions are available only on respective receiver.

readVarInt(byteBuf)

form will not be available in Kotlin, so these functions only appear after

byteBuf

(I’m not arguing your design, just trying to help get a reasonable workaround)

Every time I auto-implement a method of an interface, IntelliJ always puts the new method at the top of the class. Is there any way to change this behavior so that new methods are inserted at the bottom of the class?

There was an auto ordering plugin, very complete. I don't know if is still maintained

@dh44t Do you recall the name of the plugin?

it seems like is not maintained

but I don't know if the reason is 'cause now is embedded in IJ

by embedded do you mean there’s somewhere i can access this in settings?

yeah

I think so, I'm trying to remember

What do you think about adding special highlighting for extension member calls on nullable receiver types? I think the following code looks really weird when you don't know that

baz

is declared as an extension on `Bar?`:

foo?.bar().baz()

...

fun Bar?.baz() { }

is there a quick way to apply an intention to multiple lines? Selecting more than one either removes the intention from the list or only does it on the last line (depending on where the caret(s) is/are)

(in this case, I'm trying to

Convert concatenation to template

)

Hit

right

key and choose scope to apply

Oops, this one is not available in wider scope…

Hah, oh well. I can file an issue for it, if it should be available

@User uploaded a file: and commented: For some QFs it is. May be this one worth it as well, please file a kotl.in/issue