vshesh
Hi everyone,
I’m struggling to understand behaviours and dynamic dispatch. The example in the getting started with elixir page doesn’t make any sense to me:
defmodule Parser do
@callback parse(String.t) :: {:ok, term} | {:error, String.t}
@callback extensions() :: [String.t]
def parse!(implementation, contents) do
case implementation.parse(contents) do
{:ok, data} -> data
{:error, error} -> raise ArgumentError, "parsing error: #{error}"
end
end
end
Where does the implementation come from?
I tried using this myself when writing a module and I am doing something wrong, just not clear what. I don’t understand how to use the implementation’s functions when writing the handle_call method:
defmodule Program do
use GenServer
@callback inputs() :: [atom]
@callback init(term) :: any
@callback handle_data(any, map, map) :: term
@callback emit(term) :: map
@impl GenServer
def init(arg) do
## How do I use the implementation's inputs function? there's no implementation passed in here
__MODULE__.inputs
|> Enum.each(fn x -> Phoenix.PubSub.subscribe :inputs, x end)
{:ok, {%{}, __MODULE__.init(arg)}}
end
@impl true
def handle_call(%OSC.Message{address: address, arguments: arguments}, _, {inputs, state}) do
data = get_latest_reading(address, arguments)
newinputs = %{inputs | address => data}
# Same question in this area
if map_size(newinputs) === length __MODULE__.inputs do
newstate = __MODULE__.handle_data(state, inputs, newinputs)
__MODULE__.emit(newstate)
|> Enum.map(fn {k, v} -> Phoenix.PubSub.broadcast(:outputs, k, v) end)
{:noreply, {newinputs, newstate}}
else
{:noreply, {newinputs, state}}
end
end
def get_latest_reading(address, arguments) do
receive do
%OSC.Message{address: ^address, arguments: args} ->
get_latest_reading(address, args)
after 0 -> arguments
end
end
end
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
Other Trending Topics
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security










Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
eksperimental
You are about right.
This is the real implementation.
If you just want to use
use X, you need to add@behaviour Xinside your using macroAlso Liked
pickme467
Hi,
I believe there is no magic in dynamic dispatch. What might be missing in the example is how to use parse!
As I understand it you use parse the following way (assuming you have JSONParser defined):
I hope that helps,
Pawel
eksperimental
I think you are mixing up concepts. Behaviours is just a way to define callbacks that must be implemented, and some can be optional.
usecan be used in behaviours and protocols to define generic definitions of these callbacks, but nothing stops you from usinguseout of these situations.As @pickme467 there is no magic in behaviours, the magic happens with
useunless you read the source code you never know what’s happening behind the scenes.You could achieve
JSONParser.parse!("some string"), you would have to define it in yourParser.__using__/1macro and calluse ParserLast Post!
eksperimental
Yes. that’ s correct.
Regarding your second question, what I can recommend you is do not use
use Xto start with, see whereuse GenServerwill go, and if it makes sense where you will have to define the callbacks. Then try to abstract things intoX.__using__/1and see what will make the best use ofuse X. rememberusejust inserts code. You can pretty much copy and paste and port the quoted parts. You will figure it out.