Skip to main content

KotlinBytes: The Spread(*) Operator



I have posted a similar article on a different style on linked-in which is a 2 min read, and it tries to cut to the point without any jibber jabbers ;) feel free to check it out (here is the link).

Since you have taken the long path with interest to the full story lets dive in, The current item of the sprint at work was offline-implementation for the feature i am already working on, so i had an implementation already for bulk get call for the list screen, and i wanted is same exact implementation but this time for the detail screen so a single get call, Like most people i started to duplicate the function and modify the param and tweek the implementation to match the new requirement but then i kinda realised that i will have to modify this later as i  move further, so i kinda looked around the internet and couldn't find any right solution except passing it as a list with only one item, this felt really wrong.

 I tried asking ChatGPT and she gave me complicated solutions which i did not like or understand, i thought why not use varargs with the type T and just convert the list to an array, since thats exactly what varargs are internally so i decided to try it out and for the SINGLE GET it worked gracefully but for BULK GET i tried to convert it to a typed array but the lint slapped a TypeMismatch error as shown in the image below: 


Now that's a dead end is what i thought, but before let me check with ChatGPT for a solution, and voila i discovered the Spread Operator in Kotlin, and definitely like me many may have no clue about this operator and if enlightened they could effectively  refractor their code base better as this avoids the need of duplicate code let that be less 5 lines of code or 50 then hell yeah we do it!

Here is something i did not discuss on the other small article that is useful (later added it), reserved to the special reader ;) though it does the magic, there is minor setback for this approach.

As you might already know vararg is a special type and it takes in single item, multiple items or arrays as we discussed above but the thing is it can also be empty. Can you go thorough the following code and find the caveat iam trying inferring?



Im sure you did, yeah since the lint and compiler will be quite if i don't pass any argument then it could silently carry a bug, but it can be easily debugged but you wont't be able to enforce it, but mostly all of us are conscious coders 😆 so lets hope no one messes this up..

Hope this article was helpful and you found it insightful, if there are issues or suggestions you are most welcome to share it below or via DM (eknath.dev) :)

Thanks for reading the raw content this far ✨

Labels:

Comments

Post a Comment

Popular posts from this blog

Implementing In-app and pre-locale language selection in Android

Modern Android App Architecture One of the essential features for a globalized app is the ability to provide users with the option to choose their preferred language within the application. In this blog post, we will guide you through the process of implementing in-app language selection in an Android app. Step 1: Create Locale String Resource Create a string resource file for each respective locale by navigating to res > new > Android Resource File . Select Locale and create a string.xml file. Copy and paste the translations of your app content into these files. Step 2: Configure Locale Preferences In the res/xml folder, create a new file called locales_config.xml and specify the locales of your choice. for example look at the following code: <?xml version="1.0" encoding="utf-8"?> <locale-config xmlns:android="http://schemas.android.com/apk/res/android"> <locale andro...
Post a Comment
Read more

Chocolate Feast - Problem Solving - Hacker Rank Solution.

The expectation is to find the total number of choclate one can consume by taking full advantage of the offer, Here there are 3 inputs n which holds the value of initial amount of money for buying choclate, c is the cost price of each candy if paid by cash and m is the exchange rate for the candy. Inputs n Initial cash to buy candy. c Coast of each candy if paid by cas.h m Exchange rate for a new candy in offer. The initial count of choclate will be the cash / coast and the wrappers in hand will be the same value of choclate, and from there we loop through until the wrap count is less than the exchange rate, inside the loop the choclate count will still hold the same fourmula as before but divided with exchange rate. The wrap count is the tricky part... the wrap will be wrap/ exchange rate(the no. choclate) + the remainder of this division(THIS IS VERY IMPORTANT) because for example if the count of wrapper is 3 and the exchange rate is 2 you can only buy 1 c...
Post a Comment
Read more

Search Textfield with options and clear button ideal for app TopBar- Jetpack Compose Component

In this blog post, we'll explore a simple yet effective implementation of a search bar in Jetpack Compose. The provided SearchTextField composable offers a basic text field with a placeholder, suitable for building the app top bar. Screen Shot of the Component from my Jot-app The following code can be used to your project directly and it should work as expected, the idea was to have a search bar for a top app which can also hst the buttons on either ends,do check the code below If you have any suggestions or improvements for the code, let's have a conversation below. Your feedback is valuable to me
Post a Comment
Read more