dergraf
Here’s a bit of a geeky thought experiment: Parameterized Modules (aka “Abstract Modules”) were an experimental feature in Erlang that never left the experimental stage and were ultimately abandoned in R16.
It got me thinking—if Elixir had such a feature, could it have influenced the way libraries like Ecto, Phoenix, or Ash were implemented, particularly when it comes to component-building abstractions?
Additionally, I wonder if Parameterized Modules might have offered interesting alternatives for implementing Protocols in Elixir. Their dynamic dispatch nature seems like it could align with what parameterized modules were designed to address.
Would this feature have simplified certain patterns, or would it have introduced unnecessary complexity?
I’m curious to hear thoughts, especially from those who’ve used both Elixir and Erlang and can reflect on how parameterized modules might (or might not) fit into Elixir’s design philosophy.
Where Next?
Trending in Discussions
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
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #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.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
binarytemple
I experimented with parameterized modules when they were available. In practice, they were simpler than they might have appeared at first glance. When you ‘initialized’ a module with a constructor argument, it merely created a reference with that initial value. Subsequent function calls on that module would automatically receive this initial value as their first argument - functionally similar to how Elixir’s pipe operator (
|>) works today. While you could achieve comparable functionality using Erlang parse transforms, they were (and remain) significantly more cumbersome compared to Elixir’s elegant macro system.