mmport80
A colleague came to me with something similar to the following puzzle,
iex(9)> defmodule Record do defstruct [a: 1, b: 2, c: 3] end
iex(10)> defmodule State do defstruct [d: 4, e: 5, f: %Record{}] end
iex(13)> record1 = %State{}
%State{d: 4, e: 5, f: %Record{a: 1, b: 2, c: 3}}
iex(14)> record1 = %{record1 | f: %Record{c: 9}}
%State{d: 4, e: 5, f: %Record{a: 1, b: 2, c: 9}}
iex(15)> record2 = %{record1 | f: %Record{a: 9}}
%State{d: 4, e: 5, f: %Record{a: 9, b: 2, c: 3}}
iex(16)> record3 = %{record2 | f: %Record{c: 9}}
# problem is here… ":a" is "1" again
%State{d: 4, e: 5, f: %Record{a: 1, b: 2, c: 9}}
iex(17)> record4 = %{record3 | f: %Record{a: 9, c: 9}}
OK, stupid.
I see the problem, we are creating new records each time : )
Interesting how trying to explain a problem, also solves it : ))
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
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!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
peerreynders
I think you may be seeing the remnants of a statement based mindset. Because from the script it isn’t clear whether you actually wanted different records or whether you are simply advancing the state of the same conceptual record - for which Elixir does allow rebinding.
The script still has that imperative “do this, then do that” kind of feel (which is typical for scripts anyway but I assume that the original code looked like that as well).
I personally have no qualms having lots of well-named single line functions that also use argument pattern matching for destructuring; essentially allowing for “composed functions” (not necessarily in the FP sense and not always with the pipeline operator) so that if possible the code can look more like a progressive flow of value transformations rather than some step by step recipe.
mmport80
yeh normally I do
|>all the way, and (luckily) never find myself in this situation…