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.
Trending in Discussions
Hey there,
It’s been more than a year since we started using LiveView as our main UI library and building a whole library of UI componen...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
I’ve been using Emacs as my main code editor for more than a two years. It’s a custom build version although I’ve tried doom emacs and sp...
New
Hi there! :wave:
@frigidcode and I (but mostly him) have been running an Elixir Book club, we’re almost done with Designing Elixir Syste...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
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
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Just published claude-code-elixir, a plugin marketplace for Claude Code with Elixir support. These are the plugins I’ve been using for my...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
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










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
chrismccord
This is indeed the case of how
enforce_keysbehaves. Where are you seeing otherwise? Perhaps the docs could be clearer but the current behavior is exactly as describedilya-kolpakov
In my view, the keys are always in the struct as long as they are listed in definition:
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_keysdoes is that it makes sure the corresponding values cannot benil. Hence these are not the keys that are “enforced” byenforce_keys. It is rather the non-nilness of values that is enforced. Hence the nameenforce_keysis 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
Sorry, I was saying that your ideal view is the current behavior. For example:
Enforce keys doesn’t care about nil values, only keys. Does that clear things up?
ilya-kolpakov
Oh I see. So keys listed under
enforce_keysmust 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.