96

I want to enumerate through an array in Swift, and remove certain items. I'm wondering if this is safe to do, and if not, how I'm supposed to achieve this.

Currently, I'd be doing this:

for (index, aString: String) in enumerate(array) {
    //Some of the strings...
    array.removeAtIndex(index)
}

10 Answers 10

78

In Swift 2 this is quite easy using enumerate and reverse.

var a = [1,2,3,4,5,6]
for (i,num) in a.enumerate().reverse() {
    a.removeAtIndex(i)
}
print(a)
Sign up to request clarification or add additional context in comments.

3 Comments

Works but filter is really the way to go
@Mayerz False. "I want to enumerate through an array in Swift, and remove certain items." filter returns a new array. You are not removing anything from the array. I wouldn't even call filter an enumeration. There is always more than one way to skin a cat.
rigth, my bad! Pla dont skin any cats
58

You might consider filter way:

var theStrings = ["foo", "bar", "zxy"]

// Filter only strings that begins with "b"
theStrings = theStrings.filter { $0.hasPrefix("b") }

The parameter of filter is just a closure that takes an array type instance (in this case String) and returns a Bool. When the result is true it keeps the element, otherwise the element is filtered out.

8 Comments

I'd make explicit that filter doesn't update the array, it just returns a new one
Parentheses should be deleted; that's a trailing closure.
@Antonio you're right. Indeed that's why I posted it as a safer solution. A different solution could be considered for huge arrays.
Hm, as you say this returns a new array. Is it possible to make the filter method into a mutating one then (as I've read the mutating keyword enables functions like this to alter self instead)?
@Gee.E certainly you can add an in place filter as an extension on Array marking it as mutating and similar to the question's code. Anyway consider that this might not always be an advantage. Anyway every time you remove an object, your array might be reorganised in memory. Thus it could be more efficient allocating a new array and then make an atomic substitution with the result of the filter function. The compiler could do even more optimisations, depending on your code.
|
46

In Swift 3 and 4, this would be:

With numbers, according to Johnston's answer:

var a = [1,2,3,4,5,6]
for (i,num) in a.enumerated().reversed() {
   a.remove(at: i)
}
print(a)

With strings as the OP's question:

var b = ["a", "b", "c", "d", "e", "f"]

for (i,str) in b.enumerated().reversed()
{
    if str == "c"
    {
        b.remove(at: i)
    }
}
print(b)

However, now in Swift 4.2 or later, there is even a better, faster way that was recommended by Apple in WWDC2018:

var c = ["a", "b", "c", "d", "e", "f"]
c.removeAll(where: {$0 == "c"})
print(c)

This new way has several advantages:

  1. It is faster than implementations with filter.
  2. It does away with the need of reversing arrays.
  3. It removes items in-place, and thus it updates the original array instead of allocating and returning a new array.

2 Comments

what if item is an object and i need to check it, {$0 === Class.self} doesn't work
@TomSawyer you could write { $0 is CustomClass }
14

When an element at a certain index is removed from an array, all subsequent elements will have their position (and index) changed, because they shift back by one position.

So the best way is to navigate the array in reverse order - and in this case I suggest using a traditional for loop:

for var index = array.count - 1; index >= 0; --index {
    if condition {
        array.removeAtIndex(index)
    }
}

However in my opinion the best approach is by using the filter method, as described by @perlfly in his answer.

1 Comment

but unfortunatelly it has been removed in swift 3
5

No it's not safe to mutate arrays during enumaration, your code will crash.

If you want to delete only a few objects you can use the filter function.

3 Comments

This is incorrect for Swift. Arrays are value types, so they are "copied" when they are passed to functions, assigned to variables, or used in enumeration. (Swift implements copy-on-write functionality for value types, so actual copying is kept to a minimum.) Try the following to verify: var x = [1, 2, 3, 4, 5]; print(x); var i = 0; for v in x { if (v % 2 == 0) { x.remove(at: i) } else { i += 1 } }; print(x)
Yes you are right, provided that you know exactly what you're doing. Maybe I didn't express my response clearly. I should have said It's possible but it's not safe. It's not safe because you're mutating the container size and if you make a mistake in your code, your app will crash. Swift's all about writing safe code that won't unexpectedly crash at runtime. That's why using functionnal programming functions such as filter is safer. Here's my a dumb example: var y = [1, 2, 3, 4, 5]; print(y); for (index, value) in y.enumerated() { y.remove(at: index) } print(y)
I just wanted to distinguish that it's possible to modify the collection being enumerated in Swift, as opposed to the exception-throwing behavior of doing so when iterating through NSArray with fast enumeration or even C#'s collection types. It's not the modification that would throw an exception here, but the possibility to mismanage indexes and go out of bounds (because they had decreased the size). But I definitely agree with you that it's usually safer and clearer to use the functional programming type of methods to manipulate collections. Especially in Swift.
2

Either create a mutable array to store the items to be deleted and then, after the enumeration, remove those items from the original. Or, create a copy of the array (immutable), enumerate that and remove the objects (not by index) from the original while enumerating.

Comments

1

The traditional for loop could be replaced with a simple while loop, useful if you also need to perform some other operations on each element prior to removal.

var index = array.count-1
while index >= 0 {

     let element = array[index]
     //any operations on element
     array.remove(at: index)

     index -= 1
}

Comments

0

I recommend to set elements to nil during enumeration, and after completing remove all empty elements using arrays filter() method.

2 Comments

That works only if the stored type is an optional. Note also that the filter method doesn't remove, it generates a new array.
Agree. Reversed order is better solution.
0

Just to add, if you have multiple arrays and each element in index N of array A is related to the index N of array B, then you can still use the method reversing the enumerated array (like the past answers). But remember that when accessing and deleting the elements of the other arrays, no need to reverse them.

Like so, (one can copy and paste this on Playground)

var a = ["a", "b", "c", "d"]
var b = [1, 2, 3, 4]
var c = ["!", "@", "#", "$"]

// remove c, 3, #

for (index, ch) in a.enumerated().reversed() {
    print("CH: \(ch). INDEX: \(index) | b: \(b[index]) | c: \(c[index])")
    if ch == "c" {
        a.remove(at: index)
        b.remove(at: index)
        c.remove(at: index)
    }
}

print("-----")
print(a) // ["a", "b", "d"]
print(b) // [1, 2, 4]
print(c) // ["!", "@", "$"]

1 Comment

It's far better to have an array of struct instead of a bunch of separate arrays.
-2

2024 answer

Since this important question only has very old answers, some of which mention the current features/syntax incompletely, here's the current answer with no cruft and a full example of the syntaxes.

Traditionally (in most languages / milieu) to delete from an array you work through it backwards.

In modern Swift do not do that, do this:

var things: [Thing]

things.removeAll{ thing in

    // your code block returns Bool
    print("checking \(thing.field)")
    // your calculations
    // your calculations
    return yourBooleanResult
}

or in simpler situations

things.removeAll{ $0.length > 7.0 }

This is O(n), which is good news. It does preserve the original order and you can use it on any mutable collection.

https://developer.apple.com/documentation/swift/substring/removeall(where:)

This interesting document

https://github.com/apple/swift-evolution/blob/main/proposals/0197-remove-where.md

.. touches on the dangers and inefficiencies of different approaches to removing items from a collection, explains the shuffle down algorithm etc.

Now that this exists there is no situation where you would use "hand made" code (typically iterating backwards, etc) for the job when using Swift.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.