purely functional data structures okasaki (pdf)
recursive slowdown

How can I efficiently implement a list data structure where I can have 2 views to the head and end of the list, that always point to a head a tail of a list without expensive calls to reverse. i.e:

```start x = []
end x = reverse start -- []
start1 = [1,2,3] ++ start
end start1 -- [3,2,1]
```

end should be able to do this without invoking 'reverse' but simply looking at the given list from the perspective of the list being in reverse automatically. The same should hold if I create new lists from concatenations to start.

You could always just use `Data.Sequence`.

Alternatively, a well-known implementation of a purely functional queue is to use two lists. One for enqueue and another for dequeue. Enqueue would simply cons with the enqueue list. Dequeue takes the head of the dequeue list. When the dequeue list is shorter than the enqueue list, refill it by reversing the enqueue list. See Chris Okasaki's Purely Functional Datastructures.

Even though this implementation uses `reverse`, the amortized time cost of this is insignificant asymptotically. It works out so that for every enqueue, you incur a time debt of Θ(1) for the dequeue list refill. The expected time of a dequeue is therefore at most twice that of an enqueue. This is a constant factor, so the worst-case cost of both operations is O(1).

Efficient Amortised and Real-Time Queues in Haskell, A queue is a datastructure that provides efficient—O(1)—operations to remove an element from the front of the queue and to insert an element  A queue is a datastructure that provides efficient—O(1)—operations to remove an element from the front of the queue and to insert an element at the rear of the queue. In this blog post we will discuss how we can take advantage of laziness to implement such queues in Haskell, both with amortised and with worst-case O(1) bounds.

This question appears as the third result on the first page while I google `Haskell queue`, but the information previously given is misleading. So, I feel there is a need to clarify a few things. (And the first search result is a blog post which contains a careless implementation...)

Everything below is basically from Okasaki's paper, Simple and efficient purely functional queues and deques in 1995 or his book.

Okay, let's begin.

1. A persistent queue implementation with amortised O(1) time complexity is possible. The trick is to reverse the list representing the rear part of a queue as long as the front part is long enough to amortise the cost of `reverse` operation. So, instead of reversing the rear part when the front part is empty, we reverse it when the front part is shorter than the rear part. The following code is from the appendix of Okasaki's book

```data BQueue a = BQ !Int [a] !Int [a]

check :: Int -> [a] -> Int -> [a] -> BQueue a
check lenf fs lenr rs =
if lenr <= lenf
then BQ lenf fs lenr rs
else BQ (lenr+lenf) (fs ++ reverse rs) 0 []

head :: BQueue a -> a
head (BQ _ []    _ _) = error "empty queue"
head (BQ _ (x:_) _ _) = x

(|>) :: BQueue a -> a -> BQueue a
(BQ lenf fs lenr rs) |> x = check lenf fs (lenr + 1) (x:rs)

tail :: BQueue a -> BQueue a
tail (BQ lenf (x:fs) lenr rs) = check (lenf-1) fs lenr rs
```
2. And why is this amortised O(1) even used persistently? Haskell is lazy, so `reverse rs` does not actually happen until it is needed. To force `reverse rs`, it has to take |`fs`| steps before reaching the `reverse rs`. If we repeat `tail` before reaching the suspension `reverse rs`, then the result will be memorised so at the second time it takes only O(1). On the other hand, if we use the version before placing the suspension `fs ++ reverse rs`, then again it has to go through `fs` steps before reaching `reverse rs`. A formal proof using (modified) Banker's method is in Okasaki's book.

When the dequeue list is empty, refill it by reversing the enqueue list

is the implementation in Ch 5 of his book with a warning in the very beginning

Unfortunately, the simple view of amortization presented in this chapter breaks in the presence of persistence

Okasaki described his amortised O(1) persistent queue in Ch 6.

4. So far, we have been talking about amortised time complexity only. It is actually possible to eliminate amortisation completely to achieve the worst-case O(1) time complexity for persistent queue. The trick is that `reverse` has to be forced incrementally every time a de/enqueue is called. The actual implementation is a bit hard to explain here, though.

Again, everything is in his paper already.

Queues in Haskell – Rafal's Blog, I am steadily improving my Haskell, and in this post I will implement a First-In First​-Out Queue. Requirements. push an element onto a queue  The data structure in Data.Sequence is a faster queue and also supports a wider variety of operations. Queues with constant time operations, from Simple and efficient purely functional queues and deques , by Chris Okasaki, JFP 5(4):583-592, October 1995.

Is Data.Dequeue what you are looking for?

(It doesn't have `reverse` but you can add it pretty easily and send a patch to the author.)

Data.Queue, Queues with constant time operations, from Simple and efficient purely functional queues and deques, by Chris Okasaki, JFP 5(4):583-592, October 1995. Codementor Haskell Expert Heinrich Apfelmus has been using Haskell as his programming language of choice for over a decade now. He maintains and develops several open source libraries, including reactive-banana (a library for functional reactive programming) and threepenny-gui (a browser-based GUI framework).

I'm not really a Haskell user, but I found a blog post which claims to describe a Haskell queue that can be operated on in amortized constant time. It's based on a design from Chris Okasaki's excellent Purely Functional Data Structures.

Case Study: Okasaki's Lazy Queues, Let's see how to enforce that invariant with LiquidHaskell. To efficiently implement a queue we need to have rapid access to both the front as well as the back  A type class carrying an altered set of functional dependencies used to constrain queues when the type of the queue never escapes far enough for a more deliberate choice to be made.

Recommended queue package? (x-post from /r/haskellquestions , Recommended queue package? (x-post from /r/haskellquestions). Is there a recommended and/or standard queue implementation for Haskell? I see several​  If the input graph is empty, just output an empty graph. When the queue is empty, output the BFS tree we recursively built. Otherwise, call the function again with the input graph, the BFS tree plus the have-not-seen-yet neighbors, the queue minus the current vertex plus the neighbors we haven’t seen yet, and all of the seen or added-to-the-queue-already vertexes.

A simple queue implementation in Haskell, While this is some pretty idiomatic haskell, you definitely didn't implement the challenge the way it was intended to be solved. Either way: here's  Dan Doel - Introduction to Low Level Haskell Optimization; a video of Dan Doel's talk at the Boston Haskell Meetup, Sept 17, 2014 . Don Stewart's Haskell performance overview on StackOverflow (2013) There are plenty of good examples of Haskell code written for performance in the The Computer Language Benchmarks Game

Efficient Amortised and Real-Time Queues in Haskell, Efficient Amortised and Real-Time Queues in Haskell. Posted on January 15, 2016. A queue is a datastructure that provides efficient—O(1)—operations to  queue' = enqueue numberOfPeopleWhoJustGotInfected queue (numberOfPeopleWhoJustBecameSymptomatic,queue'') = dequeue queue Since enqueue and dequeue would always be atomic and the queue length would be fixed, I wrote a fixed length queue data structure. endequeue models the atomic enqueue & dequeue sequence.