ryanzidago
Hi all,
How to implement a queue in Elixir with O(1) insertion and O(1) deletion using a list zipper?
According to this blog post on zippers, one can use a list zipper to have a queue-like behaviour:
Zipper lists are conceptually simple enough to be easy to reinvent and replace with queues.
Considering the following zipper:
defmodule Zipper.ListZipper do
defguard is_range(range) when is_struct(range, Range)
def new, do: {[], []}
def from_list(list) when is_list(list), do: {[], list}
def from_range(range) when is_range(range), do: from_list(Enum.to_list(range))
def to_list({prev, next}), do: Enum.reverse(prev) ++ next
def prev({[], next}), do: {[], next}
def prev({[head | tail], next}), do: {tail, [head | next]}
def current({_, []}), do: nil
def current({_, [current | _]}), do: current
def pop({_, []} = lzip), do: {nil, lzip}
def pop({prev, [current | tail]}), do: {current, {prev, tail}}
def next({prev, []}), do: {prev, []}
def next({prev, [head | tail]}), do: {[head | prev], tail}
def replace({prev, []}, val), do: {prev, [val]}
def replace({prev, [_ | next]}, val), do: {prev, [val | next]}
def put({prev, next}, val), do: {prev, [val | next]}
def delete({prev, []}), do: {prev, []}
def delete({prev, [_ | next]}), do: {prev, next}
end
If I insert the sequence 1, 2, 3 into the list zipper, the current will point to the last element 3:
iex(9)> ListZipper.new()|> ListZipper.put(1) |> ListZipper.put(2) |> ListZipper.put(3)
{[], [3, 2, 1]}
Now, I could use next to move the current to the first inserted element everytime I call put/2 (unless the zipper has only one element):
iex(10)> ListZipper.new()|> ListZipper.put(1) |> ListZipper.put(2) |> ListZipper.next() |> ListZipper.put(3) |> ListZipper.next()
{[3, 2], [1]}
However, I still need to go through the whole list to get the second element 2 :think
Is it possible, or did I misunderstood the quoted sentence in the blog post?
Trending in Questions
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
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
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Other Trending Topics
Hi everyone,
Over several Elixir projects I kept writing down what each one taught me and turning the setups I got right into something ...
New
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
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ryanzidago
Looking at the queue implementation in Elixir in rosettacode, I get the gist of it.
We use two queues, (input/output queues). When we want to pop, the input queue becomes the output queues and is reversed. Next time we want to pop, we won’t need to reverse the output queue (because it isn’t empty).
This is not always O(1) but it looks like a good compromise.
lud
I think the Erlang queue module implements kind of the same thing. When you call
:queue.new()it yelds a similar initial state:{[], []}.