Sorry, my previous comment was not very clear.

What I mean to say is that, once you have a query expression at the root, then Ecto assumes you are not using keyword lists. Otherwise someone may try to write this:

where: [bar: equals_parent(...)]

And it won’t work.

I think this should fix, but I haven’t tried it:

defmacro equals_parent(parent_name, fields) do
  fields
  |> Enum.map(fn field ->
    {field, quote(do: Ecto.Query.parent_as(unquote(parent_name)), unquote(field))}
  end)
  |> Enum.reduce(quote(do: unquote(&1) and unquote(&2))
end

And it has the benefit that it can now compose with other expressions: where: equals_parent(…) or x.y == z.

IIUC, I shouldn’t need the ^ caret / interpolation operator because the macro outputs the keyword list at compile time.

I believe the keyword list only works outside of macros. You can’t use it with query expressions. Once you have query expressions, then you need to write or and and, no keyword lists.

I am unsure why would you think this even compiles.

Given they are asking why it doesn’t work, that is not helpful feedback. Expecting things to work when they don’t is part of coding (and vice-versa)!

With macros generally you want to complare what the code you want to produce looks like in AST form and then make sure your macro returns the same AST.

You can get the AST from

quote do 
  [code]
end