Just style or does it actually make a difference to

import <somelibrary>.*

as opposed to specifying the exact element(s) of the library? Presumably the only processing implication is during build, but is the value of the precision in self documentation, and is it worth it?

Sun did - there's one from 1997: https://www.oracle.com/technetwork/java/codeconventions-150003.pdf

I love standards, except where I don't agree 😎

Why I didn’t find this document after looking for it several times in the past 20 years as a Java developer is beyond me. 🙈 Thank you a lot.

Do detekt (and ktlint) enforce the official code style for Kotlin?

@Stefan Oltmann, on that (those) detekt page(s) you referred to, what is "debt"? I assume it's something to do with extra processing time, but "5 min"??? (I did search on the site, but of course extra page has "debt" on it 😞)

Technical debt. An estimate of how much time it would take for someone to fix it

I’m certainly not an expert in kotlinc, but it’s quite unlikely that wildcard imports will cause any issues apart from hiding the details about the API you’re using. That said, when using any linter, the first thing I allow as ‘OK’ is wildcard imports.

If you have two packages imported that happen to have classes of the same name you need to specify explicitly which you want. It’s not a big thing. I disallow wildcard imports on my projects because I like the explicit statement which classes I want. The block is usually automatically collapsed, so it doesn’t matter how many lines there are.