Vertigo

Vertigo

Reading/practicing through “Functional Web Development with Elixir, OTP and Phoenix”, I came across the following module definition;

defmodule IslandsEngine.Rules do
  alias __MODULE__

  defstruct state: :initialized,
            player1: :islands_not_set,
            player2: :islands_not_set

  def new(), do:
    %Rules{}

  def check(%Rules{state: :initialized} = rules, :add_player), do:
    {:ok, %Rules{rules | state: :players_set}}

  ...
end

What is the reason for the first agument’s right hand side declaration (‘= rules’) is it simply a definition of the working variable within scope ?

def check(%Rules{state: :initialized} = rules, :add_player), do:
{:ok, %Rules{rules | state: :players_set}}

Running iex -S mix I see no practical difference passing in a different ‘variable’ name or direct struct, but perhaps I am missing something obvious;

Interactive Elixir (1.7.1) - press Ctrl+C to exit (type h() ENTER for help)
iex(1)> alias IslandsEngine.Rules
IslandsEngine.Rules
iex(2)> things = Rules.new()
%IslandsEngine.Rules{
  player1: :islands_not_set,
  player2: :islands_not_set,
  state: :initialized
}
iex(3)> Rules.check(things, :add_player)
{:ok,
 %IslandsEngine.Rules{
   player1: :islands_not_set,
   player2: :islands_not_set,
   state: :players_set
 }}
iex(4)> Rules.check(%IslandsEngine.Rules{state: :initialized}, :add_player)
{:ok,
 %IslandsEngine.Rules{
   player1: :islands_not_set,
   player2: :islands_not_set,
   state: :players_set
 }}

First 6 of 6 Posts Switch mode

peerreynders

peerreynders

What is the reason for the first agument’s right hand side declaration (’= rules’) ?

rules is the same as in:

def check(rules, :add_player), do:

the difference is that

def check(%Rules{state: :initialized} = rules, :add_player), do:

adds the constraint of a pattern match.

NobbZ

NobbZ

Anything that matches the pattern %Rules{state: :initialized} will be bound to rules in the function body.

Vertigo

Vertigo OP

Thanks for replying!

I reasoned that meanwhile.., two related questions;

  • Is there strict order rules, e.g. can it also be rules = %Rules{…} instead ?
  • Why doesn’t it complain about the other two keys that are defined within the module’s struct definition?
peerreynders

peerreynders

Pattern matches on maps aren’t exact. The map can contain information in addition to the data that is matched.

peerreynders

peerreynders

  • Is there strict order rules, e.g. can it also be rules = %Rules{…} instead ?

IIRC that order will work as well.

Why doesn’t it complain about the other two keys that are defined within the module’s struct definition?

Complain about what? It’s a pattern - not a value. The pattern doesn’t care about the player1: and player2: keys and their values.

AlchemistCamp

AlchemistCamp

Yep, both orders work. Great book you’re going through, BTW!

— All posts loaded —

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
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
spammy
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
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
roeland
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
bottlenecked
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
rahultumpala
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 Top

JesseHerrick
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
mcass19
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Damirados
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
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
ausimian
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

We're in Beta

About us Mission Statement