cblavier
Hey there 
I have the 2 following structs.
defmodule Variation do
@enforce_keys [:id, :attributes]
defstruct [:id, :description, :attributes, :slots, :block]
end
defmodule VariationGroup do
@enforce_keys [:id, :variations]
defstruct [:id, :description, :variations]
end
I would like to pattern match both structs at once, based on the fact they share similar attributes: :id and :description.
Is this achievable through behaviors?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
fuelen
Another options:
Also Liked
JohnnyCurran
Just treat them as maps:
And if you need to access the underlying module:
michallepicki
You can define a Protocol and have separate implementation for each struct
michallepicki
If you want to share the implementation of a function from a protocol, you can move it to a different module and delegate there from all separate protocol implementations. Or you can create a separate protocol for the shared parts and pass a list of struct modules (or primitive types if applicable) to
defimpl.