Got a bug report on KotlinPoet regarding the following scenario:

enum class RenderPassCreate(override val value: Int) {
    companion object
}

This is the code we currently generate, and it will not compile, with the error being

Expecting ';' after the last enum entry or '}' to close enum class body

. The compiler expects the following:

enum class RenderPassCreate(override val value: Int) {
    ;
    companion object
}

which in my opinion looks ugly. I wonder if there’s a hard technical limitation behind this, and whether the compiler could handle this better? Tried searching YouTrack and it doesn’t look like it’s been filed

How do you expect the compiler to know

companion

isn't one of the enum's values? As a side note, what is the purpose of an enum without values?

both are good points

In vulkan, some enums have no entries yet and are reserved for future use.

@Dominaezzz Interesting. That seems... pointless, but that may just be because I've never done any Vulkan development.

It's done so they don't have the situation where they have to make a

vkCreateRenderPass2(...)

method because

vkCreateRenderPass(...)

doesn't take a

RenderPassCreate

parameter. It's also consistent with all the other

vkCreateSomeObject

methods that take a

SomeObjectCreate

parameter that have actual entries.

So you always pass in null for now? Or can you just not call the function yet?

Yeah, always pass null.