Skip to main content

Blog: Fixed in Size, Flexible in Power - Arrays in Kotlin

Blog: Fixed in Size, Flexible in Power - Arrays in Kotlin

Day 30! Today I took a deep dive into Arrays. If you think you know arrays from Java or C++, Kotlin has some surprises in store that make them much more developer-friendly.

Beyond the Basics

Creating an array in Kotlin feels very modern. Instead of just a fixed size and curly braces, I learned about the Array constructor. It lets you define exactly what goes into each index using a lambda.

val squares = Array(5) { i -> i * i }

It’s like a factory and a loop rolled into one!

The Performance Trap

One of the most important things I learned was the difference between Array<Int> and IntArray. - Array<Int> is an array of objects. It’s flexible but can be slow. - IntArray is a true primitive array. No boxing, no overhead—just pure speed. If you're doing heavy math or processing large amounts of data, IntArray is your secret weapon.

The == Pitfall

If you've ever tried to compare two arrays using == and gotten false even though they look identical, you've hit the referential equality wall. In Kotlin, == for arrays checks if they are the exact same instance. To check the data inside, you use .contentEquals(). It’s a simple rule, but vital for avoiding bugs!

The Spread Operator

Passing an array to a function that takes variable arguments (varargs) used to be a bit clunky. Kotlin makes it "explode" with the Spread Operator (*). It’s such a satisfying syntax: printAll(*myArray).

Multidimensional Ease

Multidimensional arrays are just arrays of arrays, but Kotlin makes them easy to work with. I especially appreciated .contentDeepToString(), which finally makes printing a matrix as easy as printing a single number.

Summary

Arrays in Kotlin provide a perfect balance: the performance of the underlying JVM primitive arrays with the high-level, expressive syntax we expect from a modern language.

Check out the full technical breakdown!

Kotlin #Arrays #Performance #CleanCode #ProgrammingJourney #JVM #DataStructures

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