ilya-kolpakov

ilya-kolpakov

By defining a struct one guarantees that the instances’ keys are exactly those provided in the definition. By including a key within the enforce_keys attribute one ensures that the corresponding values cannot be nil.

In my view, the attribute name enforce_keys suggests that the keys listed there will be always present in the struct (which is actually the case for all keys provided in the definition) rather than that the corresponding values cannot be nil.

Showing Posts 1 to 4

chrismccord

chrismccord

Creator of Phoenix

This is indeed the case of how enforce_keys behaves. Where are you seeing otherwise? Perhaps the docs could be clearer but the current behavior is exactly as described :slight_smile:

ilya-kolpakov

ilya-kolpakov OP

In my view, the keys are always in the struct as long as they are listed in definition:

iex(1)> defmodule A do defstruct [:a, :b] end
iex(2)> %A{}
%A{a: nil, b: nil}

In my view, one could say that “all the keys listed in the definition are enforced to be present in the struct instance”. And by looking at code itself one could expect that “enforce_keys” does exactly that (meaning the presence of keys not listed under “enforce_keys” within the struct is optional).

What enforce_keys does is that it makes sure the corresponding values cannot be nil. Hence these are not the keys that are “enforced” by enforce_keys. It is rather the non-nilness of values that is enforced. Hence the name enforce_keys is somewhat misleading and non-transparent (IMO).

Docs are fine. IMO, guess clear docs are not a substitute for clear unambiguous names (as they obviate the need to look in the docs in the first place).

EDIT: hopefully better explanations

chrismccord

chrismccord

Creator of Phoenix

Sorry, I was saying that your ideal view is the current behavior. For example:

iex(1)> defmodule A do
...(1)>   @enforce_keys [:name]
...(1)>   defstruct [:name, :age]
...(1)> end
{:module, A,
 <<70, 79, 82, 49, 0, 0, 8, 128, 66, 69, 65, 77, 65, 116, 85, 56, 0, 0, 1, 14,
   0, 0, 0, 27, 8, 69, 108, 105, 120, 105, 114, 46, 65, 8, 95, 95, 105, 110,
   102, 111, 95, 95, 9, 102, 117, 110, 99, ...>>, %A{age: nil, name: nil}}
iex> %A{age: 1}
** (ArgumentError) the following keys must also be given when building struct A: [:name]
    expanding struct: A.__struct__/1
    iex:3: (file)

iex> %A{name: nil}
%A{age: nil, name: nil}

Enforce keys doesn’t care about nil values, only keys. Does that clear things up?

ilya-kolpakov

ilya-kolpakov OP

Oh I see. So keys listed under enforce_keys must be present in the constructor and that’s all. They are, in a sense, like positional args to functions as they need to be always present.

— All posts loaded —

Where Next? Top

Trending in Discussions Top

AstonJ
As the title says, please share what you’ve been up to with Elixir. Whether that’s been learning it, looking into it, making stuff with i...
2977 92995 915
New
caslu
I want to open this thread for you all to discuss and help those who really like Ash but are still hesitant to use it in a real project. ...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
GES233
I’m posting this in response to Jose’s recent tweet (Cr. link) : People are sleeping on Elixir for a coding harness: Hot-code swappi...
New
_mfierro
Hello, I wrote Stop My Hand, a Scattergories-like web application using Phoenix/LiveView as my learning project for Elixir (after readin...
New
marciol
It would be helpful to have a list of companies worldwide that hire engineers without prior experience in Elixir. Often, it can be quite ...
New
durvia
Anyone running long-lived stateful processes on BEAM? We’re building an AI agent runtime and would love to compare notes. We’re a small ...
New

Other Trending Topics Top

garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
marciok
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; 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
wintermeyer
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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews