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
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #iex
- #elixirconf-us
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










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:{[], []}.