A modern programming language that makes developers happier.

kotlinlang

Hi folks, i am developing an SDK for my application's APIs and i have come across a dilemma, in requests like `getAccount(): Accounts` do you prefix your entities or not? Thanks in advance for any answer !

What do you mean? Something like `ExampleAccount` vs just `Account` ?

In regular cases like Account the conflict with the consumer app is pretty much guaranteed

If you're one of the mainstream libraries like Okio, you can go for brevity: `Buffer` , `Source` , `Sink`

If i prefix only the most common (ExampleAccount) ones and the other which the conflict is quite hard to happen to leave them as they are, it would be weird?

you can avoid the conflict where it is happening using `as` on the import 

Yea, alias imports are a solution but I don't feel super comfortable about them

&gt;  If i prefix only the most common (ExampleAccount) ones and the other which the conflict is quite hard to happen to leave them as they are, it would be weird?
I'd vote for consistency first but then again OkHttp is a counter-example. They have `OkHttpClient` and `Response`

So I guess "it depends" each one personal taste

This is one of the very few places where I miss scala - the ability to import a package is really nice.

I prefer this:
```import com.mything.web
import com.bank

val webAccount: web.Account
val bankAccount: bank.Account```
to having to alias as you would in Kotlin.

Maybe <@U0J2TNBAP> or <@U0BFDUP0E> can help us to understand that naming decision

<@UMXTNACBY> you can workaround it by wrapping it with an object, and based on the file in which you are working you use Foo.Bar or you import Foo and use only Bar

Not a bad idea for `as`: if i were the consumer i wouldn't mind it, but i guess it depends on the consumer.

<@UE206C71V> I don't follow - I'm assuming I don't control one or both of the types, I'm just a client of them. I can't nest a typealias inside an object.

<@UMXTNACBY>
Im a bit confused, can we not write something like this in kotlin?:
```val myServer = org.x.myProject.workhorse.entities.Server```


I gather Kotlin had the ability to import a package but it was removed. There's this issue asking for it back:
<https://youtrack.jetbrains.com/issue/KT-9242/Consider-returning-import-package>
but it's from 7 years ago.

<@U02R2P1J3TJ> but partial import doesn’t work based on what <@UMXTNACBY> said

<@U02R2P1J3TJ> yes, but that's really verbose particularly if you use the type a lot. In my example I'm only namespacing the type to the immediate parent package, not to the fully qualified package.

Two recommendations:
• don’t be afraid of short names: `Request`, `Call`, `Json`, `Path`
• don’t be afraid of short package names `okio`, `okhttp3`

Very few programming languages have a `com.mycompany` prefix in their naming, and as far as I know the actual collisions in practice don’t come

If you get a collision, like say `okio.Path` and `java.nio.file.Path`, you can just fully-qualify the Okio one