owaisqayum
I am going through Streams in Dave Thomas’s book and here I am having difficulties in understanding the following program.
For, example what is receive in sleep function and why to use it?
What is after in sleep function?
How this whole program is executed?
Why Dave Thomas suddenly jumped to such a complex program just after explaining the basics of Stream.
defmodule Countdown do
# sleep mode
def sleep(seconds) do
receive do
after
seconds * 1000 -> nil
end
end
def say(text) do
spawn(fn -> :os.cmd('say #{text}') end)
end
def timer do
Stream.resource(
# start of next minute or number of seconds in a minute
fn ->
{_h, _m, s} = :erlang.time()
60 - s - 1
end,
# wait for the next second
fn
0 ->
{:halt, 0}
count ->
sleep(1)
{[inspect(count)], count - 1}
end,
# nothing to deallocate
fn _ -> nil end
)
end
end
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #security
- #elixirconf-eu
- #api
- #forms
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
slouchpie
I don’t see
requirein thesleepfunction. Did you mean “receive”?owaisqayum
ohh yes, its a typo. I mean
receivesabiwara
I think you will get a better picture of how
receiveworks when reading the chapter on Processes (chap 15), in the meantime you can just consider that this is a way of sleeping.He could probably as well have used the built-in function
:timer.sleep/1, e.g.seconds |> :timer.seconds() |> :timer.sleep().The use of
receivehere is not very clear about the intent, but it is basically listening for a message that is never going to come (no call tosendanywhere) with a timeout ofseconds, after which it returns.owaisqayum
Thats pretty good explanation. Also the Stream.resource function is very confusing as one function pass data to another and thats how it traverse. Is it important to learn it at this stage or it’s too early to dive deep into it ?
LostKobrakai
It works that way not because there’s no
send– other processes could send messages – but because there’s no “matching clause” forreceive.sabiwara
Indeed, thank you for the correction
I meant to say “it isn’t trying to actually receive anything, and isn’t sending anything either, just relying on the timeout as a way to implement the sleep”.
sabiwara
While it might not be necessary to “dive deep”, it is probably helpful to understand what exists, what is possible, and you can always come back to it once you need it. The example from the doc might give you a good idea as well.
As stated in the intro, this book is “not a top-to-bottom reference guide”, don’t look at it as a checklist of things you “have to” know, but as a guide to explore the language
owaisqayum
Thanks a lot … Is there any reference book for Elixir
sabiwara
I suppose it depends what you are looking for, it is a bit hard for me to answer. Maybe this list might help?
If I had to recommend myself, I would suggest starting with the official Getting Started guide and check Elixir School as well.
A great way to explore different parts of the language through practice could be Elixir-koans.
And if you are planning to use Elixir for web development, the Phoenix official guide and Programming Phoenix are fantastic.
All those resources are free (except the book) and should help you get started, check what works best for you. Past some point nothing beats practicing on some real projects IMHO (and the official documentation will be a tremendous help once you do). And you can always come back at Programming Elixir later for a deeper dive into the concepts.
hernytan
Streams, Enums and the functional idioms can be hard to memorize. My advice is to not worry too much about memorizing every function, but learn one everytime you solve a new problem. When I was learning F#, I started with map, reduce and filter only. Then, everytime i solve a problem, I would consult the list of functions, and see if any of them applied. Sometimes I’d miss out things I could do, but that’s ok.
Now when I am learning Elixir, I do the same thing. Also, you can always come here and ask for improvements