saleyn

saleyn

Is there a way to create a macro called required that could be used like this:

with required(var) <- Map.get(map, key) do
  var
else
  nil -> raise RuntimeError
end

I tried something like this, but it doesn’t work:

defmacro required(var) do
  quote do
    unquote(var) when not is_nil(var)
  end
end

Showing Posts 1 to 4

kip

kip

ex_cldr Core Team

I don’t think a macro can return just the match part of a with (but happy to be wrong). Nevertheless, this looks more complex that the use case demands. Map.fetch!/2 does basically the same thing:

iex> Map.fetch!(%{a: "a"}, :a)
"a"
iex> Map.fetch!(%{a: "a"}, :b)
** (KeyError) key :b not found in: %{a: "a"}
    (stdlib 4.0) :maps.get(:b, %{a: "a"})

so you could simply:

with value <- Map.fetch!(map, key) do
  do_something()
end

Even in this case, its not very idiomatic since with’s value is to program “happy path” and therefore the with seems redundant in this example and the following would be the simplest:

var = Map.fetch!(%{a: "a"}, :a)
saleyn

saleyn OP

While Map.fetch!/2 is a viable option for simple cases, consider:

def some_fun(map) do
  with \
    {:ok, param1} <- wrap(map, :param1), 
    {:ok, param2} <- wrap(map, :param2),
    ...,
    {:ok, paramN} <- wrap(map, :paramN)
  do
    ...
  end
  ...
end

def wrap(map, param) do
  case Map.get(map, param) do
    nil -> {:error, :badarg}
    val -> {:ok, val}
  end
end

If we wanted to get rid of the wrapper, we could do:

def some_fun(map) do
  with \
    p1 when not is_nil(p1) <- Map.get(map, :param1), 
    p2 when not is_nil(p2) <- Map.get(map, :param2),
    ...,
    pN when not is_nil(pN) <- Map.get(map, :paramN)
  do
    ...
  else
    nil -> {:error, :badarg}
  end
  ...
end

But wouldn’t it be nice to be able to do:

def some_fun(map) do
  with \
    required(p1) <- Map.get(map, :param1), 
    required(p2) <- Map.get(map, :param2),
    ...,
    required(pN) <- Map.get(map, :paramN)
  do
    ...
  else
    nil -> {:error, :badarg}
  end
  ...
end

Maybe there is a way to come up with such a required/1 macro that would only add a single when guard to the AST?

keep_zen

keep_zen

In the FP, there is a functor named Maybe.
I think Maybe can replace the with.
Like:

defmodule Fp do
   def maybe_of({:ok, v}), do: {:maybe, v}
   def maybe_of({:error, _}=v), do: v
   def maybe_of(v), do: {:maybe, v}
  
  def map({:error, v}, onError: handler) do
     (not v && handler.(v)) |> maybe_of()
  end
  def map({:maybe, v},fun) do
     (v && fun.(v) || v)
    |> maybe_of()
  end
 def map({:maby, v}, fun) do
    (v && fun.(v))
   |> maybe_of()
 end
end
Map.get(map, :field_name)
|> Fp.maybe_of()
|> Fp.map(step1)
|> Fp.map(step2)
|> Fp.map(onError: errorHanlder)
kip

kip

ex_cldr Core Team

Perhaps I’m missing something, but this is very similar (but not the same) to:

  with \
    {:ok, p1} <- Map.fetch(map, :param1), 
    {:ok, p2} <- Map.fetch(map, :param2),
    ...,
    {:ok, pn} <- Map.fetch(map, :paramN)
  do
    ...
  end

The difference being that if the key exists and its value is nil then it will still pass unlike your example. Normally when I see use cases like “required” its a data validation case and changesets become a good tool of choice.

— All posts loaded —

Where Next? Top

Trending in Questions Top

katta
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
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
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
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
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
budgie
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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews