Skip to main content

Passing parameters into a Swift method and modifying their values

So for people who have read my blog or who know me, they would probably know that I am a Java developer in my day job(full-time contract) and coding Swift is something that I do in my spare time. So there is one thing that I do every now and again in Java and that is something like this

public void modifyCollection(List<String> collection) {
    collection.add("one");
    collection.add("two");
    collection.add("three");
}
and the method is invoked as follows

List<String> testCollection = new ArrayList<String>();
modifyCollection(testCollection);

So after the line modifyCollection(testCollection); the testCollection will have strings one, two and three. Now let us trying something similar in Swift

func modifyCollection(collection:[String]) {
    collection.append("one")
    collection.append("two")
    collection.append("three")
}

var strArray:[String] = [String]()
modifyCollection(strArray)

You will get an error i.e. Immutable value of type [String] only has mutating members named append. 

Problem

The issue is, we are not passing parameters by reference, so what we need to do is pass a parameter by reference. Great, how do we do that? well, read on to find out.

Solution 

So in general there is a specific way in which we can pass parameters by reference into a Swift method using inout parameters. So in the apple docs, there is section called In-Out Parameters, which gives a detailed explanation of what the inout parameters are all about. Now, to make the above code have the same behaviour as our Java code, we need to modify the Swift code as follows,

func modifyCollection(inout collection:[String]) {
    collection.append("one")
    collection.append("two")
    collection.append("three")
}

var strArray:[String] = [String]()
modifyCollection(&strArray)


Comments

Popular posts from this blog

Upload to AWS S3 from Java API

In this post, you will see code samples for how to upload a file to AWS S3 bucket from a Java Spring Boot app. The code you will see here is from one of my open-source repositories on Github, called document-sharing. Problem Let’s say you are building a document sharing app where you allow your users to upload the file to a public cloud solution. Now, let’s say you are building the API for your app with Spring Boot and you are using AWS S3 as your public cloud solution. How would you do that? This blog post contains the code that can help you achieve that. Read more below,  Upload to AWS S3 bucket from Java Spring Boot app - My Day To-Do (mydaytodo.com)

Addressing app review rejections for auto-renewing subscription in-app purchase (iOS)

The ability to know what the weather is like while planning your day is a feature of  My Day To-Do  Pro and as of the last update it’s also a part of the  Lite version . Unlike the Pro version it’s an auto-renewing subscription based  in-app purchase (IAP)  in the Lite version. What means is that when a user purchases it, the user only pays for the subscription duration after which the user will be automatically charged for the next period. Adding an  auto-renewing  subscription based IAP proved to be somewhat challenging in terms of the app store review i.e. the app update was rejected by the App Review team thrice because of missing information about the IAP. Therefore in this post I will share my experiences and knowledge of adding auto-renewing IAP in hopes to save someone else the time that I had to spend on this problem. In-App purchase This year I started adding IAPs to My Day To-Do Lite which lead to learning about different types of IAP...

Ionic app with a Django backend: Part 2 - The Ionic app

In this post, I will continue from where we left in Part 1 of this series.  In part 2, I will talk more about the front-end side of things. Ahh, I have a background in web development, hence I call this front-end, but that's not the most accurate thing to say in these modern times. So the right way to say this is, I will talk about the Ionic app in this Github repository(IonicAppWithRestBackend) in more details in this post. So what did we do in part 1? In part 1, we got to the point of running our backend on the web server that ships with Django . To refresh your memory, this is how we got the backend server running, Clone the repo git clone https://github.com/cptdanko/IonicAppWithRestBackend Navigate to the backend project directory cd IonicAppWithRestBackend/backend/python_django/restBackend/ Note: if you are using Windows, you may want to change "/" to "\" in the above command. Once there you can run the backend server with the follow...