Skip to main content

Step-by-Step Explanation: Kotlin Type Casts

Step-by-Step Explanation: Kotlin Type Casts

Kotlin provides high-level constructs for checking and converting types safely, combining strict compile-time checks with automatic type conversions.

1. Type Checks with is and !is

The is operator checks if an expression matches a specific type at runtime. Its negative counterpart !is checks if it does not match.

if (obj is String) {
    // obj is checked as String
}

2. Smart Casts

Smart casting is the Kotlin compiler's ability to automatically cast a variable to a specific type after a type check has been performed, avoiding manual or redundant castings. - if Condition Scopes: Once checked, the variable changes type inside the if body. - Logical Conjunction (&&): The variable is smart cast on the right-hand side if checked on the left. - when Expressions: In each branch matching a type check, the variable is smart cast automatically.

3. Unsafe Cast Operator (as)

The as operator executes an explicit, forced conversion to a specific target type. - If the runtime instance type is incompatible with the target type, a ClassCastException is thrown. - To handle potential null values, you must explicitly cast to a nullable type target (as String?).

4. Safe Cast Operator (as?)

To prevent unexpected crashes from failed casts, Kotlin provides the as? operator. - If the cast succeeds, it returns the cast value. - If the cast fails or the instance is null, it gracefully returns null instead of throwing an exception.

5. Generics Type Erasure and Star Projections

Due to JVM type erasure, generic type arguments are only checked at compile time and are not preserved at runtime. - You cannot check if an object is a List<String> directly at runtime using is List<String>. - Instead, you must use a star projection check (is List<*>) to verify it is a List, followed by an unchecked cast (as List<String>).

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 ...