its own line, just for the sake of stopping the debate 🧌

What is the most idiomatic way to define a logger on a class? In java we'd use a

static

field and I understand that you can use a

companion object

along with

@JvmStatic

but I don't like the looks of that at all.

If you really don’t like the companion object approach for some reason, a top-level

val

will also do the trick

Ya and in my case all of my loggers are on "singleton beans" so I guess I am not worried about storing a logger on each instance. (nice name btw)

Just don't use

@JvmStatic

🤔

with kotlin-logging you make either your object or companion object extend

KLogging()

, which holds a

val logger

it looks as short as this sometimes:

companion object: KLogging()

It has been corrected in the repo but never pushed to production

@svtk ^

Those set/get overloads are nice

thanks. Although I ran into a weird restriction where it was unable to figure out whether to use

Vector.plus(w: Vector)

or

Vector.plusAssign(w: Vector)

when I would use e.g.

A[i, l..n] += s * U[k, l..n]

. I'm pretty sure if it can't decide if to do either

A.set(i, l..n, A.get(i, l..n).plus(s * U.get(k, l..n)))

or

A.get(i, l..n).plusAssign(s * U.get(k, l..n))

. The former would get recorded into the matrix (and what I want), and the latter would not. Is it possible to bake a default priority into the language or is that a bad idea? Is there a priority system to annotations that I could use or could be implemented in the language?

how do i import assert in gradle for kotlin native?

nothing. create a KEEP, weigh implications, propose the feature, let the language committee rule on it

anyone have any thoughts as to why

..

is

rangeTo

as opposed to

until

?

I am trying to figure out polymorphism in kotlinx serialization with no success. Here's the code I am trying to run

@Serializable
@Polymorphic
data class JsonMessage(
    @Polymorphic val command: JsonCommand
)

@Serializable
@Polymorphic
open class JsonCommand

@Serializable
@Polymorphic
data class NewL2SnapCommand(
    val symbol: String
) : JsonCommand()

@UnstableDefault
fun main() {
    val message = JsonMessage(
        NewL2SnapCommand(
            symbol = "ABC"
        )
    )

    val snapJson = Json.stringify(JsonMessage.serializer(), message)
    println(snapJson)
}

This results in

Exception in thread "main" kotlinx.serialization.SerializationException: class jsonApi.NewL2SnapCommand is not registered for polymorphic serialization in the scope of class jsonApi.JsonCommand

The documentation for this is kinda sparse since it's a new feature, so any help would be appreciated.

hi, I'm new to kotlin and Android development

I was trying to do things right and use coroutines in a piece of functionality that makes http requests. First I had to discard Ion because it's not good for coroutines. I had to discard Fuel because it doesn't compile to Android API 16. I had to discard asynkio because it was hijacking the async/await calls in Kotlin. Finally I am using kohttp, but what the hell? what a ride man

even for kohttp, there's a asyncHttpGet but no asyncHttpPost so I had to implement that...

so far, I'm missing typescript/node, hell, I'm missing C++

@Felix Robles Have you tried the Retrofit library?

thanks for the tip though!

Imagine the following scenario: The goal is to write a type for a name of a syntactic element. The name can either be simple or qualified. And the name can either describe a package, type or method. We would like to ensure at compile time that certain methods can only accept any kind of qualified/simple name (be it package, type or method) or any kind of type/package/method name (be it simple or qualified) or any combination thereof. I came up with the following:

class Name<K : Name.Kind, E : Name.NamedElement>(val kind: K, val namedElement: E) {
	sealed class Kind {
		object Simple : Kind()
		object Qualified : Kind()
	}

	sealed class Element {
		object Type : Element()
		object Package : Element()
		object Method : Element()
	}
} 

fun onlyQualifiedNames(n: Name<Name.Kind.Qualified, *>)
fun onlyMethodNames(n: Name<*, Name.Element.Method>)
fun onlySimplePackageNames(n: Name<Name.Kind.Simple, Name.Element.Package>)
fun anyName(n: Name<*,*>)

What do you think? It feels way over engineered. If we were only interested in either qualified/simple or type/package/method then I would use sealed classes of course. But here we have a 2-dimensional relationship.

https://twitter.com/kotlin/status/1125398218756567046 More than 1.5 million people used Kotlin for all types of development in 2018, most of it in production! Get more figures and infographics at https://t.co/grVpmI0CUe #KotlinCensus18 https://t.co/vnJfGD2cXX Twitter

Kotlin Census 2018 Infographics and Report Kotlin 1.0 was released 3 years ago. It has been an amazing journey and a huge achievement to get to where we are today: Kotlin/Native has opened up incredible possibilities for Kotlin usage on all platforms, Kotlin was announced as … Continue reading →

I could not find a way to write that kind of

for

loop in Kotlin

what do you recommend to use for a fifo queue with limited size (only last x elements)?

I don't exactly know what this kind of

for

is called, but I find it useful quite often, and I can't really replace it with

for (i in x..y)

🙌hello! I’m one of the organisers of Kotliners, an all-day conference about everything Kotlin. We just published our final lineup - keynotes by @jonnyzzz (JetBrains) and Wojtek Kaliciński (Google), followed by two parallel tracks (one focusing on the cutting edge, the other on practical Android development). Save the date - 7th of June, Budapest, Hungary. You can check out the event here: https://www.conferenceforkotliners.com

If somebody is on Google IO today or just want to discuss it, please join #google-io google

https://twitter.com/kotlin/status/1125852733528002562 We’re launching #KotlinEverywhere - a global series of community-led events - supported by @googledevs and @JetBrains - where you can learn more about #kotlin, including using it in #Android, #GCP and #multiplatform development. Find out more at https://t.co/s11wpDeaNP https://t.co/FpxjCLAD1Q Twitter

Kotlin Is Everywhere! Join the Global Event Series When we say ‘Kotlin is everywhere’, we mean it. Kotlin works on all platforms, and it allows you to develop all types of applications. Developers are excited about Kotlin and hungry for opportunities to learn more. Now it’s time to … Continue reading →