Skip to main content

Step-by-Step Explanation: Kotlin Types Overview

Step-by-Step Explanation: Kotlin Types Overview

Kotlin's type system is designed to be unified and efficient. Here is a breakdown of the core concepts.

1. Everything is an Object

In Kotlin, you don't have "primitives" like int in Java. Instead, you use Int, which is a class. This means you can call methods on it:

val x = 10.plus(5) // Equivalent to 10 + 5

At runtime, the Kotlin compiler optimizes these into primitives for performance whenever possible, but as a developer, you always work with objects.

2. Basic Type Categories

  • Numbers: Byte, Short, Int, Long, Float, Double.
  • Booleans: true and false.
  • Characters: Char (enclosed in single quotes 'K').
  • Strings: String (enclosed in double quotes "...").
  • Arrays: Array<T> (created with arrayOf(...)).

3. The Root of Everything: Any

Any is the counterpart to Object in Java. Every class in Kotlin has Any as its ultimate superclass. It provides three methods: equals(), hashCode(), and toString().

4. The Result of "Nothing": Unit

Unit is used as the return type of functions that don't return a meaningful value. It is similar to void in Java, but Unit is a real object (a singleton instance).

5. The Value That Never Is: Nothing

Nothing is a special type that has no instances. It is used to represent values that never exist. For example, a function that always throws an exception:

fun fail(msg: String): Nothing {
    throw Exception(msg)
}

If a function returns Nothing, the compiler knows that the code following the call will never be reached.

6. Verification

Verified by building the project. The implementation demonstrates the unified type system and the existence of special types like Unit and Any.

Comments

Popular posts from this blog

Mastering Per-App Language Preferences: From Android 10 to Android 13+

  One of the most requested features by users is the ability to use an app in a language different from the system language. While Android 13 (API 33) introduced "Per-App Language" settings at the system level, implementing this backward-compatibly for older devices like Android 10 (API 29) used to be a challenge involving manual configuration wrapping. Today, thanks to AppCompat 1.6.0+ , we have a unified, standard way to handle this. Here is the modern guide to implementing seamless language switching. The Architecture: How it Works On Android 13 and above, the system handles the storage and application of your app's locale. On older versions, the AppCompat library manages this behavior by storing your preference in an internal XML file and injecting the resources during the activity lifecycle. Step 1: The Locale Helper Utility Instead of scattering logic across your app, use a clean LocaleHelper object. This handles the distinction between the system LocaleManager (...

Beyond Scanning: Meet the All-in-One AI Document Assistant by Digitify Vision Technology

In an era where efficiency is the ultimate currency, information is scattered everywhere—on physical paper, within QR codes, and inside lengthy digital documents. The challenge isn't just capturing this data; it’s making it work for you. At Digitify Vision Technology , we believe your smartphone should be more than just a camera—it should be a high-performance engine for your daily workflow. Today, we are proud to unveil our most powerful update yet: a total evolution in AI-driven document management. 💡 Key Features of the New Update We’ve bridged the gap between physical information and digital action by integrating advanced vision and audio intelligence into a single, seamless experience. 🔍 Precision Scanning for Everything Our advanced vision engine is now more versatile than ever. Intelligent Document Scanning: Capture crisp, professional-grade scans of physical papers, contracts, or handwritten notes. QR Code Extraction: Instantly scan any QR code to extract text, read URL...
  Optimising Android Launch: Mastering App Startup & The Modern Splash Screen The first few seconds of an app’s life determine a user's first impression. A slow start or a flickering white screen can lead to immediate uninstalls. In this guide, we’ll look at how to streamline your initialisation using the App Startup Library and ensure a seamless visual transition with the Android 12 Splash Screen API (with full backward compatibility for API 29). Part 1: The App Startup Library Traditionally, apps initialised multiple components using separate content providers. This adds overhead and slows down launch time. The Jetpack App Startup library allows all components to share a single content provider, significantly improving performance. Why use it? Performance: Shared content provider reduces overhead. Order: Explicitly set the initialisation sequence. Simplicity: Both library creators and app developers use a unified interface. Part 2: The Modern Splash Screen API Starting ...