axelson
Scenic Core Team
This is a question that originated on the Elixir Slack from David Billskog and I have made only minor changes to the module.
Given this module:
defmodule Dummy do
def execute(x) do
with var_a <- get_a(x),
var_b <- get_b(x) do
IO.inspect(var_a, label: "a")
IO.inspect(var_b, label: "b")
IO.inspect({var_a, var_b})
if var_a != var_b do
IO.inspect(var_a, label: "a")
IO.inspect(var_b, label: "b")
IO.inspect({var_a, var_b})
end
end
end
defp get_a(x) do
IO.puts("get a")
if Enum.any?(x, & &1 == "A"), do: 3, else: 2
|> IO.inspect(label: "returning a")
end
defp get_b(x) do
IO.puts("get b")
if Enum.any?(x, & &1 == "B"), do: 2, else: 1
#|> IO.inspect(label: "returning b")
end
end
Dummy.execute(["A", "B"])
I get this unexpected output:
$ elixir sample.exs
get a
get b
a: 3
b: 2
{3, 2}
a: 3
b: 1
{3, 1}
Does anyone understand what is happening here? I don’t expect for the value of b to change within the if statement, and I do expect the returning a inspect to be printed. Tested on elixir 1.11.2-otp-23 and erlang 23.0.2.
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
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
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,
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 has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
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
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 10 of 13 Posts
slouchpie
I tested this with elixir 1.11.0 and Erlang 23.1 and I get a different result:
kwando
You probably need parenthesis around the if statement for the
"returning a"part.But I’m not sure what happens with the output, seems strange that
var_bchange value.josevalim
@axelson my hunch is that you are running into an Erlang or Elixir bug. Update to Erlang 23.1 and see if it persists.
LostKobrakai
I just tried 23.1 (and 1.11.2) and can still reproduce the issue from slack. @axelson’s example doesn’t seem to cause issues for me.
axelson
Ah, yes you are correct about the reason the inspects are not printing out (I forgot about the precedence rules with
|>).axelson
I’m still seeing the issue with elixir 1.11.2-otp-23 and erlang 23.1.5
blackode
We can check how the code was developed by using
quote doThat results to
Which is always true in this case. So, it won’t enter into else
al2o3cr
Can confirm - Axelson’s example works fine on my machine (OTP23.1 / Elixir 1.11.2) and this one fails.
A colleague tried @LostKobrakai’s example on 22.2.6 / 1.11.1 and it printed
2three times, as expected…al2o3cr
Poked at it a little more. Strange things are afoot - I get different results depending on what’s on a line that never executes (OTP 23.1 / Elixir 1.11.2):
But commenting out
|> IO.inspect(label: "nope")makes it do the{3,1}thing…EDIT: bonus fact - the
1has some kind of additional significance, changing it to anything else makes the bug stop happening on my machine.dbi
I simplified the example to this and can still reproduce the odd print running macOS Catalina 10.15.7 using Elixir 1.11.2 and Erlang 23.1.5.
Simplifying it one step furter, replacing
if x == "A", do: 3, else: 2(that will always evaluate to true) intoif true, do: 3, else: 2will fix the unexpected output.