You’re second example pretty much works as is, I occasionally use a similar pattern.
I just added an extra paren for the “Space Cake” clause:
inventory = [%{id: 1, name: "Space Cake", count: 11}]
cond do
moon_cake = Enum.find(inventory, &(&1.name == "Moon Cake")) ->
{:eat, moon_cake.id}
((space_cake = Enum.find(inventory, &(&1.name == "Space Cake")))[:count] || 0) > 10 ->
{:eat, space_cake.id}
true ->
nil
end
Although if you can structure it as a single reduce it will be more performant (although you’ll need quite a long list before that will begin to matter much), but turning this into a reduce might make it more difficult to follow since it doesn’t seem like the operation you are doing is easily thought of as a transformation. Also if the clause is as complex as the “Space Cakes” clause I would probably think about restructuring the logic away from a cond, or maybe extracting a helper function.
