I m running into a weird situation where the properties of m kotlinlang #announcements

Channels

100daysofkotlin

100daysofkotlin-2021

algolialibraries

android-architecture

android-databinding

androidgithubprojects

androidx-xprocessing

arrow-contributors

beepiz-libraries

cincinnati-user-group

codemash-precompiler

codingconventions

competitive-programming

competitivecoding

compose-android

compose-desktop

compose-ui-showcase

connect-audit-events

cscenter-course-2016

domain-driven-design

effective-kotlin

effectivekotlin

embedded-kotlin

event21-community-content

fb-internal-demo

fluid-libraries

framework-elide

getting-started

github-workflows-kt

graviton-browser

image-processing

intellij-plugins

intellij-tricks

introduce-yourself

java-to-kotlin-refactoring

jhipster-kotlin

jvm-ir-backend-feedback

k2-early-adopters

kotest-contributors

kotlin-by-example

kotlin-data-storage

kotlin-foundation

kotlin-in-action

kotlin-multiplatform-contest

kotlin-pakistan

kotlinforbeginners

kotlingforbeginners

kotlinprogrammers

kotlintest-devs

kotlinultimatechallenge

kotlinx-datetime

lambdaworld_cadiz

language-evolution

language-proposals

leedskotlinusergroup

library-development

machinelearningbawas

myndocs-oauth2-server

navigation-architecture-component

ohio-kotlin-users

pattern-matching

pocketgitclient

practical-functional-programming

prozis-android-backup

python-contributors

realworldkotlin

refactoring-to-kotlin

refreshversions

russian-kotlinasfirst

skia-wasm-interop-temp

sofl-user-group

spring-security

squarelibraries

stayhungrystayfoolish

strife-discord-lib

swagger-gradle-codegen

swiss-user-group

tricity-kotlin-user-group

Title

d

dalexander

11/14/2018, 6:53 PM

I’m running into a weird situation where the properties of my companion object are static rather than being part of the companion itself. They do not have a

@JvmStatic

annotation. Anyone have any idea what’s going on? All of the documentation I can find seems to indicate that only the companion object itself should have static. This is causing problems the framework I’m using is trying to use reflection against the local properties and because they are static it’s not working. (This is on 1.3.0 in case it matters)

d

diesieben07

11/14/2018, 6:54 PM

const val

properties become

static

, too.

d

dalexander

11/14/2018, 6:55 PM

That’s good to know, but I’m using `var`s in this case.

class Foo {
    companion object {
        var temp = 3
        var bar = "asdf"

        init {
            val fields = Foo.Companion.javaClass.fields
            fields.forEach {
                println(it.name)
            }
        }
    }
}

This is the test code I’m using to try and isolate the issue.

d

diesieben07

11/14/2018, 6:59 PM

Huh, curious, I did not know that. It seems that the fields are placed in the class always, only getter and setter go into the companion.

2 Views

#announcements Join Slack