Fl4m3Ph03n1x
Is there a way to have Elixir Records without default values?
Background
I am trying to find a cheap and easy way to create New Types in Elixir, and Records seem to be just what I would need.
Problem
However, Elixir records require one to define default values. Not only that, it also allows one to create empty records (which would then be populated with said default values).
For my specific use case, this is a problem. Not only don’t I have anything that can be used as a default value, I also don’t want to allow the users of my code to create empty records.
Now, I understand this is likely a well intended choice, most likely so it can interface nicely with Erlang records, but it causes an usability issue on my end: it allows the creation of non valid data.
Questions
I understand there is probably no solution for this conundrum using Records only, so I was wondering if there are alternatives in the wild of libraries or even hacks to accomplish this.
I personally have found nothing, right now I have the feeling my only solution is to write my own macro.
- Is there a way to have Records not accept default values?
- If not, what community libraries are out there that could help fulfill the role of creating a New Type?
Marked As Solved
Fl4m3Ph03n1x
Answer
- Is there a way to have Records not accept default values?
No. This is not possible with Records. Records were never intended for this use case and forcing this abstraction into them would only complicate things. While one could use a wrapper new method, it would still be a lot of boilerplate and all the validation for type would be on the user.
- At the time of this writing, there are none. However, in another post I created a macro that achieves this purpose: How to define Macro for a new Type? - #10 by Fl4m3Ph03n1x - Questions / Help - Elixir Programming Language Forum
In that post I propose an API and then I refine it with the community’s help. For those of you who are curious, it can be used like this:
type.ex
defmodule Type do
import NewType
deftype(Name, String.t())
end
test.ex
defmodule Test do
alias Type.Name
@spec print(Name.t()) :: binary
def print(name), do: Name.extract(name)
def run_1 do
# dialyzer complains !
Name.new(1)
end
def run_2 do
# dialyzer complains !
print("john")
end
@spec run_3 :: binary
def run_3 do
print(Name.new("dow"))
end
end
Also Liked
OvermindDL1
If you want to validate data then make a constructor function for it, I generally call it new.
Popular Backend topics
Other popular topics
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Latest in Elixir
Backend>Questions
Categories:
Sub Categories:
Popular Portals
- /elixir
- /rust
- /ruby
- /wasm
- /erlang
- /phoenix
- /keyboards
- /python
- /js
- /rails
- /security
- /go
- /swift
- /vim
- /clojure
- /emacs
- /haskell
- /java
- /svelte
- /onivim
- /typescript
- /kotlin
- /c-plus-plus
- /crystal
- /tailwind
- /react
- /gleam
- /ocaml
- /flutter
- /elm
- /vscode
- /ash
- /html
- /opensuse
- /centos
- /php
- /deepseek
- /zig
- /scala
- /sublime-text
- /textmate
- /lisp
- /react-native
- /debian
- /nixos
- /agda
- /kubuntu
- /django
- /arch-linux
- /deno
- /nodejs
- /revery
- /ubuntu
- /spring
- /manjaro
- /diversity
- /lua
- /julia
- /markdown
- /c
Devtalk Sponsors
Practical resources that improve the lives of professional developers.
We build trusted fault-tolerant systems that scale to billions of users.
Real-time error tracking, performance insights, and observability for devs.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Develop your skills with books, videos, and courses.
Catch errors, track performance, monitor hosts and more.
Enabling companies to succeed by building software people love.
Courses that move you from confusion to "Aha, now I get it!"