ben-pr-p
One of my favorite new ES6 features in Javascript was the object literal shorthand, where:
const { location, venue_name } = { location: [30.2391, -99.1301], venue_name: "The Club" }
console.log(location) // [30.2391, -99.1301]
console.log(venue_name) // The Club
Additionally, I could do:
const extra_property = "some additional info"
const obj = { location, venue_name, extra_property }
But in Elixir, I find myself doing lots of
%{location: location, venue_name: venue_name} = struct
// process location and venue_name somehow
new_struct = %{location: location, venue_name: venue_name, extra_property: extra_property}
Is there any way in Elixir to do that similar struct desctructuring / creation shorthand (any way I can avoid typing venue_name twice), or how would I request it as a feature of the language in future iterations?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
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
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
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!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 5 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
DianaOlympos
This should be another thread probably but that rebuttal is soooooo missing the point. But that is because it mix Design Pattern with architecture, which is a classic problem.
peerreynders
Smartass answer #1:
Smartass answer #2:
The universal FP answer - write/use a (factory) function - e.g.:
.
new_struct = MyStruct.new location, venue_name, extra_property
Sorry, I couldn’t help myself (obviously).
Rebuttal
PS: There was a time where JavaScript was most hated for not being some other language one would much rather be working in. But I guess that was at a time where it was rare that anybody would learn to program in JavaScript first.
ben-pr-p
Oh those libraries are perfect @zimt28 – thanks!
gregvaughn
Look at the archives of the elixir-core mailing list. It’s been discussed and denied as a core language feature. Look to libraries or write your own macros/sigil if you really feel the need for it.
zimt28
You could use one of the following libraries:
https://github.com/danielberkompas/destructure
https://github.com/meyercm/shorter_maps
https://github.com/whatyouhide/short_maps