SirWerto
Good morning,
I’m using the :gen_statem erlang behaviour for modeling a process and the compiler is throwing me some warnings about bad implementations behaviours
This is the module definition
defmodule Collector.Plubio do
@behaviour :gen_statem
I am doing the calls like that
@spec state?() :: {:ok, :waiting | :collecting} | {:error, :timeout}
def state?() do
try do
case :gen_statem.call(Collector.Plubio, :current_state, 5000) do
:waiting -> {:ok, :waiting}
:collecting -> {:ok, :collecting}
end
rescue
RuntimeError -> {:error, :timeout}
end
end
And the :gen_statem.state_name/3 are like this
@impl true
def waiting({:call, from}, :current_state, state) do
{:next_state, :waiting, state, {:reply, from, :waiting}}
end
But the compiler still showing me these warnings
warning: got "@impl true" for function waiting/3 but this behaviour does not specify such callback. The known callbacks are:
* :gen_statem.callback_mode/0 (function)
* :gen_statem.code_change/4 (function)
* :gen_statem.format_status/2 (function)
* :gen_statem.handle_event/4 (function)
* :gen_statem.init/1 (function)
* :gen_statem.state_name/3 (function)
* :gen_statem.terminate/3 (function)
It is my first time calling directly and erlang behaviour so probably I am forgetting something, does someone knows how to fix that?
Thank you so much:)
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
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
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
Hello,
I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance 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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
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
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
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
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 4 of 4 Posts
kokolegorille
The error is about…
… maybe remove this?
josevalim
To add to @kokolegorille’s reply,
:gen_statemonly has a handful of static callbacks. The other callbacks are dynamic, based on your code, and those do not get a@impl true.SirWerto
yes, this fix the warning, thank you:).
But, what does the compiler expect about a
:gen_statem.state_name/3callback?Shouldn’t we mention that callback?
SirWerto
thanks for the explanation.