Compile Time Constants

A short note on compile time constants and their usage in annotations

Gabriel Shanahan
The Kotlin Primer

--

— — — — — — — — — — — — — — —

THE CURRENT VERSION OF THIS ARTICLE IS PUBLISHED HERE.

— — — — — — — — — — — — — — —

Tags: #FYI

This article is part of the Kotlin Primer, an opinionated guide to the Kotlin language, which is indented to help facilitate Kotlin adoption inside Java-centric organizations. It was originally written as an organizational learning resource for Etnetera a.s. and I would like to express my sincere gratitude for their support.

It is recommended to read the Introduction before moving on. Check out the Table of Contents for all articles.

If the value of a read-only property is known at compile time, you can mark it as a compile time constant using the const modifier.

Such a property needs to fulfill the following requirements:

  • It must be a top-level property, or a member of an object declaration or a companion object (more on both of those later)
  • It must be initialized with a value of type String or a primitive type
  • It cannot have a custom…

--

--