CommandoSev

CommandoSev

How to write a recursive function, which iterates over a list and checks if an element is in that list in elixir?

Showing Posts 1 to 6

andrewb

andrewb

You can use the Enum.any?. There is excellent documentation.

Or you can roll your own.

def do_something([], _item, data), do: data

def do_something([h | t], item, data) do
 data =  
    if h == item, do: [h | data], else: data
 do_something(t, item, data)
end

Essentially, you are doing your check and calling with the remainder of the list. I recommend looking at the Enum library it has everything you need.

CommandoSev

CommandoSev OP

What exactly is data in that code?

andrewb

andrewb

@CommandoSev it is a list acting as an accumulator. Here are some examples:

  1. Find out if something exists in a list:
list =  [1,2,3,4]

Enum.any?(list, fn item -> item == 3 end)
true

  1. If you want to get the item if it exists:
list =  [1,2,3,4]

Enum.find(list, fn item -> item == 3 end)
3

  1. If you want to find all of the matches and have them returned in a list:
list = [1, 2, 3, 4, 3]

# The second arg is the accumulator which I have named acc in the anonymous function
Enum.reduce(list, [], fn item, acc -> 
  # If true add the item to the acc list, otherwise return the acc as is
  if item == 3, do: [item | acc], else: acc  
end)
[3,3]

You can replicate the Enum.reduce function by writing your own recursive function:

list = [1, 2, 3, 4, 3]

# match on the empty list and return the accumulator
def my_reduce([], acc, _item), do: acc

# match on the head and tail of the list and test if item exists
def my_reduce([h | t], acc, item) do
acc = 
  if h == item do
   [h | acc] # add the matching item to the accumulator 
  else
   acc # no match so return acc as is
  end
 my_reduce(t, acc, item) # recursivly call my_reduce with the tail of the list and the acc
end

# start the recursive function by calling it
my_reduce(list, [], 3)

Hope this helps. If you tell us exactly what you are trying to do I am sure we can help work it out.

Andrew

kip

kip

ex_cldr Core Team

If you are new to list recursion then you might find this a way to understand the concept. Given a arbitrary list [:a, :b, :elixir, :c, :d], recursing over the items in this list is conceptually like saying “process the first element of the list, then process the rest of the list”.

In Elixir that looks like:

def process_list([first | rest]) do
  [process_element(first) | process_list(rest)]
end

Here the recursion is a very obvious implementation of the description. Process the first element, then process the rest of the list. Its recursive because the function is calling itself.

Will this work? It will to an extent. But what happens if the list is empty? Then there is no first and the function will raise an exception. So we need to cater for the empty list. And in this implementation there will always be an empty list because eventually there is no rest when the function recurses to the end. Therefore:

def process_list([]) do
  []
end

def process_list([first | rest]) do
  [process_element(first) | process_list(rest)]
end

def process_element(:elixir), do: true
def process_element(_other), do: false

This is the simplest form of recursion (and I personally think its the most beautiful) but it won’t cater for all requirements. This form will always return a list the same length as the original list. In your case thats not what you want and therefore an accumulator may be required is order to build a new list. Which is what the great examples from @andrewb do.

Aetherus

Aetherus

The recursive thinking:

  1. If the list is empty, then the thing you want to find is definitely not in that list.
  2. If the first element is what you want to find, then you found it.
  3. If the first element is not what you want to find, then find that thing in the rest of the list (which is still a list, could be empty, though)

So the code is

def exist?([], _item), do: false

def exist?([item | _tail], item), do: true

def exist?([_something_else | tail], item), do: exist?(tail, item)
eksperimental

eksperimental

There is a special case when the list has only one element, where the rest of the list will be []. You don’t need to match against [head] since [head | rest] will work, but just to keep that in mind

iex(1)> [head | rest] = [1, 2]
[1, 2]
iex(2)> head
1
iex(3)> rest
[2]

iex(4)> [head | rest] = [1]   
[1]
iex(5)> head
1
iex(6)> rest
[]

iex(7)> [head] = [1]       
[1]

iex(8)> [head] = [1, 2]
** (MatchError) no match of right hand side value: [1, 2]

Once you learn how to iterate recursively over a list, study how Enum.reduce/3 and Enum.reduce_while/3 work because pretty much everything can be implemented with these two functions. For example, your initial question could be implemented with reduce_while.

— All posts loaded —

Where Next? Top

Trending in Questions Top

katta
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
budgie
A little off-topic, but I feel like people here have a good head on their shoulders. I used to be quite good at making software. Was luc...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews