for Java compatibility, how should you allow a kotlin object (singleton) to be accessed?

It should already be accessible with

YourClass.INSTANCE

, if I'm not mistaken

I had to do:

sealed class IssueNewGiftCardResponse {
    object Issue : IssueNewGiftCardResponse()
    object Cancel : IssueNewGiftCardResponse()

    companion object {
        @JvmField val ISSUE = Issue
        @JvmField val CANCEL = Cancel
    }
}

ook, does anybody have any documentation on how the ant task

<javac><withKotlin></javac>

works?

it seems to be ignoring my

maximummemorysize

attributes

does that cause two processes to be invoked?

javac invokes kotlinc in a separate process mid-compilation?

according to this: https://github.com/JetBrains/kotlin/blob/master/ant/src/org/jetbrains/kotlin/ant/KotlinCompilerBaseTask.kt at least its all done in-process, but then i dont know much about ant's task system

You can replace the unused parameter name with a '_' character to indicate that you are ignoring it. I'm not fond of this convention myself, as I lose information about a parameter which I may care about at a later time.

but it's trivially easy to start caring and give it a name

buy the professor one of these

hey guys, I have an interesting question. I have some init { } blocks... one in an abstract class, and another in an object that extends it. Neither init block appears to execute. I am wondering if Kotlin does some kind of optimization that makes the objects initialize lazily?

i hate build systems so much. 4 replies see https://youtrack.jetbrains.com/issue/KT-16961

@User uploaded a file: Init block not executing

So the idea here is that this object extends from BlockStateSerializer, which has a companion object with a HashMap called serializersByType. This child object puts itself into the Map. Or so the expectation goes. In reality, since SignSerializer doesn't ever get called directly, init { } doesn't ever get called.

...but I want init { } to get called anyway, regardless if anyone uses SignSerializer directly or not

I tried putting this init block into the parent class (BlockStateSerializer), but it doesn't get called there either, for the same reasons.

yeah this is

I don't know what conventions are for this kind of thing, but your effectively trying to do work in a static initializer. That means you need to get this class loaded by a class loader, which you can do by running the expression

SignSerializer::class

somewhere on the program trace.

but that looks funny, espescially since people often assume what the classloader does is a pure operation

so my suggestion is to extract that static initializer into a method and simply call that method from somewhere on the program trace

yeah, sadly it defeats the paradigm I'm trying to achieve

yeah unforetunately, this is one of the bigger semantic differences between .net and java, java classes are as lazy as the sun guys could make them

which means static initializers, (or companion object initializers) are just as lazy

I have a bunch of different types of objects that I have no control over (not my objects). I want to be able to write some lightweight serializer objects that can serializer/deserialize them. And I want to do it without reflection 🙂

Sadly, both Java and Kotlin lack good annotation stuff. There's no way to say "give me all the objects that implement this annotation"

thats not quite right

you might look into a custom annotation processor, and generated code